Jonathan Rockway wrote: > Also, read http://www.catalystframework.org/calendar/2006/21 > for unicode details.
The encoding::warnings pragma is great, though I'm a little shocked at how many warnings it's uncovered. Other questions: C::P::Unicode encodes the body in the finalize method. That makes sense. But I'm tempted to try putting "use encoding 'utf8'" in the main catalyst application module. Or at least "use open 'utf8'". That would handle all the file reads and writes, but presumably also the final write to STDOUT that catalyst does. So it sounds like it would conflict with C::P::Unicode. I'll be experimenting later, but does anyone have comments on doing it like that? Thanks, Richard http://www.bbc.co.uk/ This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated. If you have received it in error, please delete it from your system. Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately. Please note that the BBC monitors e-mails sent or received. Further communication will signify your consent to this. _______________________________________________ List: Catalyst@lists.rawmode.org Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.rawmode.org/ Dev site: http://dev.catalyst.perl.org/
