> > - Make sure your database character set is utf8 > > - Make sure all your tables have a character set of utf8 > > - Make sure your database.yml has 'encoding: utf8' set for each database > > None of these steps are required officially unless you use utf-8 > specific features of the database (collation). The last setting seems > to set the connection encoding, which shouldn't be required unless > there is non-utf8 data stored in the database. > > > - Put $KCODE='u' in your environment.rb > > This is only required if you use unicode strings in your Ruby code. > > - Add an after_filter to application.rb to set the Content-Type > header correctly > > Rails now defaults to utf-8 Content-Type.
So, if we merged in ActiveSupport::Multibyte, and updated helpers like truncate to use the chars proxy, what other changes would be required to make this stuff simple? Normalisation of input parameters? Anything else? It would be nice if we could make it really easy to have this stuff 'just work' without much in the way of additional user intervention. -- 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 [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 -~----------~----~----~----~------~----~------~--~---
