Jonathan Rockway wrote:
* On Mon, Mar 03 2008, Matt Lawrence wrote:
See also the PERL_UNICODE environment variable, documented in man perlrun.
No, don't do that.
Any particular reason?
I find it pretty convenient for not having to remember to tell perl that
I have a unicode term
* On Mon, Mar 03 2008, Matt Lawrence wrote:
> See also the PERL_UNICODE environment variable, documented in man perlrun.
No, don't do that.
Regards,
Jonathan Rockway
___
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailma
Aristotle Pagaltzis wrote:
So for that one-liner, you do this:
echo 'é' | perl -MEncode -e '$_ = decode 'UTF-8', scalar <>; print /\w/'
Yes, this is tedious. So what you do is you find ways to get the
parts of your program that speak to the outside world to decode
input on receipt and encod
Hello Aristotle,
Aristotle Pagaltzis a écrit :
[Losta useful things deleted...]
For Catalyst, that means things like Catalyst::Plugin::Unicode
Great! I did not see this one :-( Thank you!
and configuring your database and template engine correctly.
This is already t
Hi Alexandre,
don’t use encoding.pm. It’s a confused and broken design, and the
author himself recommends against its use. Its main purpose is to
allow you to write code in some arbitrary encoding. As a side
effect it sets your input/output encoding, but it shouldn’t, and
confusing the encoding of
