Hi, I have stumbled upon this too. But I don't really care what the locale is called underneath. 95% of the time I'm just making a dutch-only website, so it's just a I18n.default_locale = 'nl-NL' in an initializer and done!
I'd rather see the default_url_options fixed (http://groups.google.com/group/rails-i18n/browse_thread/thread/1e06acc9a3ece0c3) You can do something like this on the vendor/rails directory if you like: find | grep en-US.yml | xargs cat $1 >> app/i18n/en/rails.yml And then some find and replace to rename en-US to the locale you want. I'd much rather have i18n_label included or a default translations directory generated by the rails command and an initializer that automatically loads that. It would create some unity in i18n implementations. I suggest the app/i18n/ directory. It's that or a rewrite of the error messages system, to solve that annoying problem that the attribute is always at the start of a message. I might do that anyway, coming weeks. -- Iain Hecker http://iain.nl/ On Thu, Nov 13, 2008 at 21:56, Sven Fuchs <[EMAIL PROTECTED]> wrote: > > I stumble across this bit every time I start doing something "real" > with Rails I18n and this makes me think. > > For Rails we've picked the default locale :"en-US" because we've > thought it'd be the most defensive claim to make. Nobody could really > argue for picking anything else because this is in fact the locale to > which Rails always (implicitely) was localized. > > But it is also artificial in that Rails I18n itself does not support > locale fallbacks (e.g. looking up :en when :"en-US" is not available) > so when we work with only Rails we either have to use en-US literally > as a locale or somehow map it manually. (E.g. when one wants to use a > route like /en/:ressource one needs to map :en to :en-US so that Rails > can find its own translations. How cumbersome.) > > I guess way more than 80% of all applications will be perfectly happy > with only supporting language locales and ignoring the country/region > tag (like :en, :fr, :es, :de, ...). > > So my feeling is that we should change the Rails default locale > from :"en-US" to just :en as long as it is still possible. > > That might expose us to arguments that we implicitely define English > as American English but on the one hand I'd say that the gained > simplicity and convenience outweighs this and on the other hand we > might argue that Rails actually always implicitely already did that. > > WDYT? > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
