On 23-aug-2006, at 14:04, Jesper Rønn-Jensen wrote:
> These are the most obvious examples I encountered while working on my
> LocalizationSimplified plugin. There are other places as well, but for
> now lets focus on the low-hanging fruit where we can easily make Rails
> core more i18n friendly.
I wholeheartedly agree but I would love to have Multibyte integrated
first, after characters are working (i18n) it
might be time to think about l10n.
There is no cause to introduce this artificial dependency. Jesper has proposed some simple steps forward -- please consider pursuing rather than undermining this path.
jeremy
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
