Jesper,

I totally agree. I'd like to take it one step further. Hardcoded strings
are a pain, even if you're *only* targeting english speaking people. It
means you cannot change the defaults even if you want those to be
English.

How hard would it be to create a patch where all the hardcoded strings
have been replaced by vars (with the same content)? Is there no way to
do that and still maintain BC with other i18n plugins?

Jeroen


Jesper Rønn-Jensen wrote:
> Below is a copy of a discussion I just posted on Rails Core mailing 
> list.
> The reason not to take the discussion here is that I think that we all 
> agree
> on that Rails sometimes can be extremely difficult to deal with on i18n
> issues. Copy below. Please share your thoughts on Ruby on Rails Core 
> list:
> http://groups.google.com/group/rubyonrails-core/browse_thread/thread/346cda3cd39e6fa9/c45615100e0f909a#c45615100e0f909a
> 

-- 
Posted via http://www.ruby-forum.com/.
_______________________________________________
Railsi18n-discussion mailing list
Railsi18n-discussion@rubyforge.org
http://rubyforge.org/mailman/listinfo/railsi18n-discussion

Reply via email to