On 26-sep-2006, at 11:16, Michael Koziarski wrote:
>> KCODE, all response charsets out of the box UTF, maybe processing the >> params with iconv according to the request-charset. > > Is the request charset sent by all browsers for all requests? How > risky is automatically translating with iconv (assuming it's > available)? Incidentally, this is what I meant by normalization, > that'll teach me to use a reserved word ;). I see almost no risk. t has to do with a browser (or a REST client, for that matter) using a wrong charset when doing the request. The server recieving the request can then decode the request into it's internal encoding. This is how (among others) Trackback system works in MovableType. But just as Thijs said. we might as well omit that. It has nothing to do with normalisation. > >> But first and foremost - clear documentation. > > What do you feel is currently missing from the > ActiveSupport::Multibyte patch? As one of the authors I feel pretty secure here. Just wanted to make sure the big README we have put there gets a visible spot in the AS docs. -- Julian 'Julik' Tarkhanov please send all personal mail to me at julik.nl --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
