Re: ActiveSupport::Multibyte for better Unicode support

> As I said in an earlier email, the laundry list reads something like:
> - Make sure your database character set is utf8 <- this should
> possibly be checked by Rails
> - Make sure all your tables have a character set of utf8 <- this
> should be done in migrations
> - Make sure your database.yml has 'encoding: utf8' set for each database

We can't change these without the users intervention, and doing utf-8
with postgres is a little harder than just 'setting the encoding' for
the table.  Perhaps this is just something we need to include in our
documentation?

> - Put $KCODE='u' in your environment.rb

We could update the railties templates, but people will still need to
manually update their application.

> - Add 'normalize_unicode_params :form => :kc' to your application.rb

Why do we need this?   I can understand the rationale for doing iconv
for 'differently encoded' strings, but can't quite follow the
justification of normalization.

> I'll sit down next week and write a plugin that does all this (if
> someone doesn't beat me to it).

Sounds good.

-- 
Cheers

Koz

--~--~---------~--~----~------------~-------~--~----~
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 rubyonrails-core@xxxxxxxxxxxxxxxx
To unsubscribe from this group, send email to 
rubyonrails-core-unsubscribe@xxxxxxxxxxxxxxxx
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-core
-~----------~----~----~----~------~----~------~--~---