NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
every Perl script that says:
"Don't be stupid."
--Larry Wall
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
unidecode, transcribe, timtowdti (Score:1)
Fortunately CPAN filenames are 7 bit and only a few of the non
\wfilenames are allowed. As much I'd like to change that as much CPAN has to be the advocate of the limitations that the last poor soul in the chain has to fight with who wants to use CPAN.I'm sure you know how to give the tarball a different name. I'm not so sure that perl is able to deal with UTF-8 module names. So please bring your first UTF-8 module into the core. I'm looking forward to see how it fares.
Reply to This
Re: (Score:2)
=head2 Properly Unicode safe tokeniser and pads.
The tokeniser isn't actually very UTF-8 clean. C is a hack -
variable names are stored in stashes as raw bytes, without the utf-8 flag
set. The pad API only takes a C pointer, so that's all bytes too. The
tokeniser ignores the UTF-8-ness of C, or any SVs returned from
source filters. All this could be fixed.
Re: (Score:1)
But package names work quite ok. I did a similar experiment at nearly the same time with Acme::Ünicöde. Locally on disc it just works fine. Once uploaded it is even installable via CPAN.pm by the dist name (eg. S/SC/SCHWIGON/acme-unicode/Acme-nicde-0.02.tar.gz). The filename problem is solveable anyhow during/after "make dist".
The only remaining problem is getting the PAUSE indexer to use the META.yml instead trying his luck on the files and to generate that META.yml with some mor