Dan Kogai <[EMAIL PROTECTED]> writes:
>On Tuesday, Dec 3, 2002, at 11:24 Asia/Tokyo, Dan Kogai wrote:
>> Aw. You can't use 'utf16' for "use encoding" or PerlIO. You have to
>> specify the endianness. Because of the BOM mark you can't use it for
>> PerlIO stream.
>
>Hmm Even with endianness
I think this was (at least partly) a wrong alarm: it seems that it's
the byte sequence 0x00 0x0a that makes groan about partial
characters. If I do things "right" and convert also the "\n" (aka 0xa)
to (little-endian) UTF-16 (0x0a 0x00), things work without warnings.
(I've not figured out yet wha
> >Aw. You can't use 'utf16' for "use encoding" or PerlIO. You have to
> >specify the endianness. Because of the BOM mark you can't use it for
> >PerlIO stream.
>
> Hmm Even with endianness strictly set PerlIO still warns w/ partial
> character warning. Should I mark all UTF as non-Perl
On Tuesday, Dec 3, 2002, at 11:24 Asia/Tokyo, Dan Kogai wrote:
Aw. You can't use 'utf16' for "use encoding" or PerlIO. You have to
specify the endianness. Because of the BOM mark you can't use it for
PerlIO stream.
Hmm Even with endianness strictly set PerlIO still warns w/ partial
char
On Tuesday, Dec 3, 2002, at 11:12 Asia/Tokyo, Jarkko Hietaniemi wrote:
Why the 'Partial character' warnings? I would have though the input
files are just right. Also, the warnings are given to stderr
unconditionally, I would have to redirect stderr to /dev/null to get
rid of the warnings.
$ per
