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
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
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
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
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.