[Catalyst] Encoding UTF8 ?

2011-03-28 Thread John M. Dlugosz
I don't understand why |Catalyst::Plugin::Unicode::Encoding| is necessary, based on the writup: it takes request arguments and converts them from whatever they came in to Perl's native encoding, and likewise for the response. But Perl is using UTF-8 in its strings anyway. So what's it have

Re: [Catalyst] Encoding UTF8 ?

2011-03-28 Thread Jorge Gonzalez
El 28/03/11 19:50, John M. Dlugosz escribió: I don't understand why |Catalyst::Plugin::Unicode::Encoding| is necessary, based on the writup: it takes request arguments and converts them from whatever they came in to Perl's native encoding, and likewise for the response. But Perl is using

Re: [Catalyst] Encoding UTF8 ?

2011-03-28 Thread Zbigniew Lukasiak
On Mon, Mar 28, 2011 at 7:50 PM, John M. Dlugosz wxju46g...@snkmail.comwrote: I don't understand why Catalyst::Plugin::Unicode::Encoding is necessary, based on the writup: it takes request arguments and converts them from whatever they came in to Perl's native encoding, and likewise for

Re: [Catalyst] Encoding UTF8 ?

2011-03-28 Thread John M. Dlugosz
On 3/28/2011 1:25 PM, Jorge Gonzalez jorge.gonzalez-at-daikon.es |Catalyst/Allow to home| wrote: Did you set ENCODING = 'utf-8' in the configuration of your TT View? Ah, thanks! That worked. I looked again carefully at

Re: [Catalyst] Encoding UTF8 ?

2011-03-28 Thread Andrew Rodland
On Monday, March 28, 2011 12:50:00 PM John M. Dlugosz wrote: I don't understand why |Catalyst::Plugin::Unicode::Encoding| is necessary, based on the writup: it takes request arguments and converts them from whatever they came in to Perl's native encoding, and likewise for the response.