> Simply put, a _character_ is no longer _one byte long_ when you get > beyond the characters you can see printed on your keyboard. Even > simple punctuation like these "double quotation marks" take up > _two bytes_ each, and stuff like ⾦ is _three bytes_ in UTF-8.
The problem with UTF-8 is that the length of characters varies. So something like this: a_string[434..2443] is no longer O(1). This is why things are often stored with ucs-2 internally, and converted at the boundaries. I believe this is how the JVM handles things, but I could be completely wrong. But Jamis' point is a valid one, I think one of the key reasons that rails has been successful is that we haven't just gone mad adding features left right and center. Everything which gets in is taken from an application where it's been proven. In other frameworks where this hasn't happened you get annoying bugs, and sub-par apis. i18n is something I care about, but it's not something I need for my paid work. I think the ideal way to get it into core is for people who are experts *and* need it in their paid work to produce a plugin. Then once the plugin has been in use by the community, we can roll it in. I18n is extremely important, i18n needs to end up in the core distribution. But we need to do it the 'rails way'. -- Cheers Koz
_______________________________________________ Rails-core mailing list Rails-core@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-core
