> 1. The specified language (fr-CA in this example) > 2. The related "generic" language (fr) > 3. Any related "sister" language (fr-FR or fr-CH) > 4. The overall default language (en-US)
I think this is too complex. IMHO, this should work exactly as class inheritance: if two classes are children of the same class, when a method is missing in one of them, they search only in the parent, never in the "sisters". And I also agree with Kip that is strange falling from fr to en. So I think that Kip implementation, at least in terms of features, is great. :) I'm just worried with performance. In Kip example, almost all translations are kept in the parent and in theory it's twice slower. But we could fix that easily by merging language files when Rails is started in production. On the other hand, it would consume more memory. :) And Sven, can we bake into I18n core a method that would return the "broader locale"? I18n.locale = 'en-US' I18n.broader_locale #=> 'en' I'm using this in Localized Templates and Kip is using also. This is probably needed. :) -- José Valim http://josevalim.blogspot.com/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "rails-i18n" 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/rails-i18n?hl=en -~----------~----~----~----~------~----~------~--~---
