On Mon, Mar 28, 2011 at 1:04 PM, John M. Dlugosz <[email protected]>wrote:
> On 3/28/2011 2:51 PM, Andrew Rodland > andrew-at-cleverdomain.org|Catalyst/Allow to home| wrote: > >> >> What engine error you noticed before? You broke threading. >> >> "Caught exception in engine "Wide character in syswrite at > /usr/share/perl5/Catalyst/Engine.pm line 675" Yes, that would be related to not encoding with the plugin. You need the plugin to encode output so you don't that that message. John, you are better off ignoring that Perl is using UTF-8 internally. All byte data that represents characters must be decoded on input -- and likewise all characters in Perl must be encoded before writing. I know I discussed this before, but is there a plan to make decoding and encoding part of Catalyst core? Seems to trip people up and it seems like something that should always be done. -- Bill Moseley [email protected]
_______________________________________________ List: [email protected] Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/
