• To: <xml-dev@l...>
• Subject: RE: Why would MS want to make XML break on UNIX, Perl, Python, etc ?
• From: Tim Bray <tbray@t...>
• Date: Thu, 20 Dec 2001 20:52:01 -0800
• In-reply-to: <5C39F806F9939046B4B1AFE652500A3A251A69@R...>

At 01:22 PM 20/12/01 -0800, Michael Rys wrote:

>XML is based on Unicode code points. XML 1.0 is based on the "textual"
>subset due to its SGML legacy and authoring focus.

Er, no.  Without prejudice to the larger issue of C0 code points,
the historical fact is that XML 1.0 deliberately chose to force all 
information content of whatever kind into a textual representation 
based on the evidence that this pays off well in terms of 
interoperability.  No more, no less. -Tim

• Follow-Ups:
  • Re: Why would MS want to make XML break on UNIX, Perl, Python, etc ?
    • From: Gavin Thomas Nicol <gtn@r...>

• References:
  • RE: Why would MS want to make XML break on UNIX, Perl, Python, etc ?
    • From: "Michael Rys" <mrys@m...>

• Prev by Date: RE: Namespace Usage Question
• Next by Date: Re: Why would MS want to make XML break on UNIX,
• 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