Jarkko Hietaniemi ([EMAIL PROTECTED]) writes:
Both input data and the script. Just because the script has been saved
in UTF-8, does not mean that literals in the script are taken as UTF-8.
Oh, great. Now you want to mix different encodings in the same file.
I give up :-)
I think you
Porters,
I have just released Encode version 2.00. Though major version has
been incremented, there is no big feature (addition|change)s.
=head1 AVAILABILITY
http://www.dan.co.jp/~dankogai/Encode-2.00.tar.gz
or CPAN near you
=head1 CHANGES
$Revision: 2.0 $ $Date: 2004/05/16 20:55:15 $
* version
No. The patch I submitted peeks at the beginning of a Perl script and
if it either sees a BOM or something that looks like raw BOMless UTF-16
(every other byte zero, every other not) of either endianness, Perl will
understand.
I think I understood that the change was only for the script as
