On Fri, Feb 20, 2009 at 6:57 PM, Jonathan Rockway <j...@jrock.us> wrote: > > Braindump follows.
snip snip > > One last thing, if this becomes core, it will definitely break people's > apps. Many, many apps are blissfully unaware of characters and treat > text as binary... and their apps kind-of appear to work. As soon as > they get some real characters in their app, though, they will have > double-encoded nonsense all over the place, and will blame you for this. > ("I loaded Catalyst::Plugin::Unicode, and my app broke! It's all your > fault." Yup, people mail that to me privately all the time. For some > reason, they think I am going to personally fix their app, despite > having written volumes of documentation about this. Wrong.) > Some more things to consider. - 'use utf8' in the code generated by the helpers? - ENCODING: UTF-8 for the TT view helper? Maybe a global config option to choose the byte or character semantics? But with the DB it becomes a bit more complex - because BLOB columns probably need to use byte sematic. -- Zbigniew Lukasiak http://brudnopis.blogspot.com/ http://perlalchemy.blogspot.com/ _______________________________________________ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/