Extension should be able to register its own translated messages about yii2 HOT 2 CLOSED

This should be considered as a design discussion, rather than a final decision of the design.

Because Yii supports different kinds of message storage, we can't assume message translations are always stored as files.

Currently, I'm introducing an I18N application component which manages message translations and possibly other I18N-related features.

I think the messageSources property can be provided by I18N. It is a list of categories mapped to the corresponding message source configurations. This property can be dynamically modified so that extensions have chance to register the message translations they use. For example:

'messageSources' => array(
    'yii\*' => array(
        'class' => ...
    ),
    'my\company\ext\*' => array(
       ....
    ),
),

When Yii::t() is called somewhere (either app code or extension code), it will use the category to locate the appropriate message source registered in messageSources. We probably should support wildcard matching of category names (e.g. yii\* matches both yii\base and yii\web). This would allow a single source to support multiple categories.

from yii2.

Done.

from yii2.