Re: DWIM with non ASCII characters

[moritz]

in reply to DWIM with non ASCII characters

What do you think is the best strategy for handling non ASCII characters?

Decode everything that comes from the outside. Encode everything that leaves your program. use utf8;. Avoid locales if you can.

See Perl, encodings and Unicode and the Perl Programming/Unicode UTF-8 WikiBook.

[Hue-Bond]

Decode everything that comes from the outside. Encode everything that leaves your program. use utf8;

Why use utf8;? As I understand the documentation, its purpose is to enable the source code to be in UTF-8 (so you can do e.g. my $ñ = 'foo'; where 'ñ' is not a single byte). It even says "Do not use this pragma for anything else than telling Perl that your script is written in UTF-8".

I thought the preferred way to decode/encode the program's input/output was by using Encode.

[ikegami]

More importantly, use utf8; allows you to do

my $foo = 'ñ';

So far, I've stuck to ASCII in my sources, so use utf8; wouldn't do anything for me.

I thought the preferred way to decode/encode the program's input/output was by using Encode.

No way. Why encode and decode everything yourself when you can let PerlIO do it. At least, that's the way I see it.

[Hue-Bond]

More importantly, use utf8; allows you to do

my $foo = 'ñ';

Hmm, then I must have configured something in my system, since I can do that without use'ing utf8:

$ xxd ñ.pl 
0000000: 7072 696e 7420 27c3 b127 0a              print '..'.
$ env -i /usr/bin/perl -Mstrict -wl ñ.pl
ñ

[moritz]

Why use utf8;? As I understand the documentation, its purpose is to enable the source code to be in UTF-8

Yes, that way you avoid concatenating decoded and non-decoded strings.

Of course it requires your script to be actually stored in UTF-8. But since the more general solution (use encoding $your_encoding) is severly broken (wrt to AUTOLOAD, thread safety and other issues), that's currently the only sane way to store non-ASCII Perl programs.

As for the rest, I can only agree to what ikegami wrote; using IO layers is much more convenient than using encode() and decode() on every IO operation. More importantly since there are fewer spots you have to care about encoding, the probability of forgetting it somewhere (and getting Mojibake in response) is much lower.