Attached is my proposed patch for the translation issue. I think we should support both conventions and deprecate neither. The newer convention is cleaner when you nest multiple models within one namespace:
en: activemodel: models: namespace: model_one: one: Model One other: Model Ones model_two: one: Model Two other: Model Twos Vs: en: activemodel: models: namespace/model_one: one: Model One other: Model Ones namespace/model_two: one: Model Two other: Model Twos The newer convention fails only when you nest models within models, which is probably uncommon compared to nesting models in modules. In that case, if you use the old namespace/model convention, the lookup following the old convention will simply fail, and I18n.translate will move on and try the namespace/model convention. So I think it's safe to support both. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
0001-Support-both-conventions-for-translations-for-namesp.patch
Description: Binary data
