Note about translations in bundle inheritance #1015
Conversation
… parent will cause translation override to happen the other way.
|
Hi Rafael! I believe you're 100% right, however I think this may not have anything to do with child/parent bundles, meaning we've just got some plain inaccurate information in this section on that topic. The translation files are all loaded into one big array, and I believe that this is done in order of how the bundles are loaded. So, it ends up having nothing to do with child/parent bundles and everything to do with populating this big pool based on order. But, I want to ping out to Twitter and see if we can get some verification on this. The behavior makes sense from a code standpoint, but it also feels a bit strange that this one situation doesn't respect the child-parent stuff. Thanks! |
|
@weaverryan indeed, translations have nothing to do with parent/child releationships. Any bundle can provide translation strings for any translation domain |
|
@weaverryan yes that is the case, its all about order. But if there is a "parent/child" override in the framework, the least it should do i guarantee that for all functionality IMHO. Also, the fact that all translations are based on order of initialization should also be made clear in the docs, it is confusing to a user that does not know the core. |
|
Thanks guys - I've merged this in (sha: 001fa07) and also clarified things considerably. The previous description on this topic related to translations was just plain wrong - it should be much better now: sha: f1355d2 @rdohms I agree that the behavior for this one type of resource seems inconsistent. I see that you already have an issue on the topic. I agree with what you guys are saying there - doc is the easiest way, but it does make logical sense to re-order the translation files (though it may not actually happen). Thanks for the report! |
Added note to alert users that initializing a child bundle before the parent will cause translation override to happen the other way.
Discussed here: symfony/symfony#3148