• To: Richard Tobin <richard@c...>
• Subject: Re: Why would MS want to make XML break on UNIX, Perl, Python, etc ?
• From: John Cowan <jcowan@r...>
• Date: Fri, 21 Dec 2001 12:46:16 -0500
• Cc: xml-dev@l...
• References: <200112211339.NAA04395@m...>
• User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.6) Gecko/20011120

Richard Tobin wrote:

> How does more on these systems behave with Latin-1, UTF-8 and UTF-16
> files, all of which are already legal?


"More" assumes that its output is a terminal, so it refuses

to send strange C0 and C1 characters to it, for fear of making
the output unreadable.  Whether "more" is encoding-sensitive,
or just assumes ASCII+, depends on the OS flavor.

-- 
Not to perambulate             || John Cowan <jcowan@r...>
    the corridors               || http://www.reutershealth.com
during the hours of repose     || http://www.ccil.org/~cowan
    in the boots of ascension.  \\ Sign in Austrian ski-resort hotel

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

• Prev by Date: IBTWSH in RNG (was: Goodbye to textual applications?)
• 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