[Rails-core] Re: RFC: Enterprise-ready internationalization (i18n) for Rails

2009-04-30 Thread geekQ
Hi, Sven Fuchs wrote: > Hi Vladimir, > > On 27.04.2009, at 18:02, geekQ wrote: >> the most important question is, whether the core team would sacrifice >> *some* parts of humanize, pluralize and other string concatenation >> voodoo, especially in ActiveRecord to al

[Rails-core] Re: RFC: Enterprise-ready internationalization (i18n) for Rails

2009-04-27 Thread geekQ
Hi, = Executive summary ;-) the most important question is, whether the core team would sacrifice *some* parts of humanize, pluralize and other string concatenation voodoo, especially in ActiveRecord to allow for 100% linguistically correct translations and smooth, enterprise-ready localization

[Rails-core] Re: RFC: Enterprise-ready internationalization (i18n) for Rails

2009-04-22 Thread geekQ
I noticed that the formatting somehow got screwed up. You may find the html version easier to read http://github.com/geekq/rails/blob/854140d9401ee25fae5b5e0f8c1436818507e796/rfc-internationalization.markdown Regards, Vladimir --~--~-~--~~~---~--~~ You received

[Rails-core] RFC: Enterprise-ready internationalization (i18n) for Rails

2009-04-21 Thread geekQ
We have been working on a Rails application for a big company, that will be rolled out in many countries. We have carefully followed Rails development over the last 8 months and tried out different tool sets for internationalization: Rails 2.1 together with the gettext 1.93 gem, ActiveSupport.I18