On 26-sep-2006, at 10:06, Michael Koziarski wrote:
> > 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. Normalization on input and before saving to the database, but this might scare some people off if used wrong. What Rails might do is adopt the Character Model for the Web and just stick to C normalizations everywhere. However I think this still might stay optional, because this might raise exceptions and loose ends in the situations where people send intrinsic bytestrings as input parameters. What I do is I had defined input norm as a filter for ApplicationController, as the step in the chain responsible for input sanitization. Implicit normalization at runtime is not the way because it transiently changes the offsets of strings as soon as you slice/ truncate/concatenate. -- 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 -~----------~----~----~----~------~----~------~--~---
