[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: Why would MS want to make XML break on UNIX, Perl, Python

• To: xml-dev@l...
• Subject: RE: Why would MS want to make XML break on UNIX, Perl, Python, etc ?
• From: "Champion, Mike" <Mike.Champion@S...>
• Date: Fri, 21 Dec 2001 07:13:29 -0700

> -----Original Message-----
> From: Richard Tobin [mailto:richard@c...]
> Sent: Friday, December 21, 2001 8:39 AM
> To: xml-dev@l...
> Subject: Re:  Why would MS want to make XML break on UNIX,
> Perl, Python, etc ?
> 
 
> How does more on these systems behave with Latin-1, UTF-8 and UTF-16
> files, all of which are already legal?

Right. That's why these various "death of text" and "can't edit with a text
editor" and "breaking Unix" threads mystify me: XML 1.0 opened the door to
all these problems. If folks have gotten by just fine using their ASCII
tools with XML 1.0, that's not likely to change with 1.1.  OK, so you COULD
get an XML 1.1 (as drafted) document with  NELs rather than LFs or various
control characters in it that may confuse vi or sed or more.  I can't
imagine that these tools handle UTF-16 gracefully, so people who are getting
by with ASCII tools are getting by because of CONVENTIONS, not STANDARDS.
The convention of sending Americans stuff in ASCII if possible, Western
Europeans stuff in ISO Latin 1, etc. is not going away any faster than the
old tools do.  

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

• Prev by Date: Re: Recently published W3C Working Drafts (long)
• Next by Date: RE: embedded html
• 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