xml-dev - Re: [xml-dev] Why would MS want to make XML break on UNIX, Perl, Python

Re: [xml-dev] Why would MS want to make XML break on UNIX, Perl, Python

[ Lists Home | Date Index | Thread Index ]

To: xml-dev@lists.xml.org
Subject: Re: [xml-dev] Why would MS want to make XML break on UNIX, Perl, Python, etc ?
From: Gavin Thomas Nicol <gtn@rbii.com>
Date: Fri, 21 Dec 2001 12:25:53 -0500
In-reply-to: <200112211335.NAA04372@mcpherson.cogsci.ed.ac.uk>
Organization: Red Bridge Interactive, Inc.
References: <200112211335.NAA04372@mcpherson.cogsci.ed.ac.uk>

On Friday 21 December 2001 08:35 am, Richard Tobin wrote:
> In article <E16HFW6-0005JX-00@server2000.ebizhostingsolutions.com> you 
write:
> >This is still not a reason to allow control codes. You know, as well as I
> > do, that they *will* cause problems.
>
> I cannot see why they would cause any problems that UTF-16 doesn't.

Sure, but then you talk about NUL being bad. UTF-16 includes a lot of zero 
bytes (as you know) so the point is moot.

Even in US-ASCII, these things are going to be an issue.

Follow-Ups:
- Re: [xml-dev] Why would MS want to make XML break on UNIX, Perl, Python, etc ?
  - From: Richard Tobin <richard@cogsci.ed.ac.uk>

References:
- Re: [xml-dev] Why would MS want to make XML break on UNIX, Perl, Python, etc ?
  - From: Richard Tobin <richard@cogsci.ed.ac.uk>

Prev by Date: Re: [xml-dev] Why would MS want to make XML break on UNIX, Perl, Python, etc ?
Next by Date: IBTWSH in RNG (was: Goodbye to textual applications?)
Previous by thread: Re: [xml-dev] Why would MS want to make XML break on UNIX, Perl, Python, etc ?
Next by thread: Re: [xml-dev] Why would MS want to make XML break on UNIX, Perl, Python, etc ?
Index(es):
- Date
- Thread