• To: xml-dev@l...
• Subject: Re: Why would MS want to make XML break on UNIX, Perl, Python, etc ?
• From: Richard Tobin <richard@c...>
• Date: Fri, 21 Dec 2001 13:35:25 GMT
• Cc:
• In-reply-to: <E16HFW6-0005JX-00@s...>
• Organization: HCRC, University of Edinburgh

In article <E16HFW6-0005JX-00@s...> 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.

Though as I said before, I don't really have much use for them myself.

>NUL is of course even worse.

That's a quite separate case.  It would break many existing interfaces,
and would definitely be a mistake.

-- Richard

• 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: Gavin Thomas Nicol <gtn@r...>

• Prev by Date: Re: 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