• To: xml-dev@l...
• Subject: Re: Why would MS want to make XML break on UNIX, Perl, Python, etc ?
• From: Gavin Thomas Nicol <gtn@r...>
• Date: Fri, 21 Dec 2001 12:24:42 -0500
• In-reply-to: <200112211339.NAA04395@m...>
• Organization: Red Bridge Interactive, Inc.
• References: <200112211339.NAA04395@m...>

On Friday 21 December 2001 08:39 am, Richard Tobin wrote:
> In article <E16HOlz-0002Yo-00@s...> you 
write:
> >On some Unices, "more" will fail to open the file, let alone display it
> >correctly.
>
> How does more on these systems behave with Latin-1, UTF-8 and UTF-16
> files, all of which are already legal?

Of course, the fail with UTF-16. UTF-8 is generally OK. The algorithm appear 
to be with codes <32 appearing in the first 128 bytes or so?

• References:
  • Re: Why would MS want to make XML break on UNIX, Perl, Python, etc ?
    • From: Richard Tobin <richard@c...>

• Prev by Date: Re: Some comments on the 1.1 draft
• Next by Date: Re: Why would MS want to make XML break on UNIX, Perl, Python, etc ?
• Previous by thread: Re: Why would MS want to make XML break on UNIX, Perl, Python, etc ?
• Next by thread: Re: Why would MS want to make XML break on UNIX, Perl, Python, etc ?
• Index(es):
  • Date
  • Thread