In my experience,
tr and Unicode don't mix well. Here's my approach (source code stored in UTF-8 encoding):
use strict;
use warnings;
use utf8;
use 5.010;
use Unicode::Normalize qw/NFKD/;
binmode STDOUT, ':encoding(UTF-8)';
sub frob {
my $str = NFKD(shift);
$str =~ s/\pM//g;
$str =~ s/[^a-z-A-z0-9]/_/g;
$str;
}
my $test = '&[]ÀÂÄàâäÇçÉÊÈËéêèëÏÌÎïìîÖÔÒöôòÜÛÙüûù?!;«»()" íóñÑáéóúÁÉÍÓ
+Ú';
say frob $test;
__END__
[]AAAaaaCcEEEEeeeeIIIiiiOOOoooUUUuuu_________ionNaeouAEIOU
Update: Since several people misunderstood me, I feel I should clarify. I wrote that in my experience, Unicode and tr/// don't mix. Which is to say that tr/// isn't buggy, but I haven't encountered any code in the wild that correctly handles Unicode strings with tr///, because tr wasn't designed with Unicode in mind.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.