• To: xml-dev@l...
• Subject: Re: Why would MS want to make XML break on UNIX, Perl, Python, etc ?
• From: Gavin Thomas Nicol <gtn@r...>
• Date: Sat, 22 Dec 2001 00:16:40 -0500
• In-reply-to: <200112220003.AAA28217@r...>
• Organization: Red Bridge Interactive, Inc.
• References: <200112220003.AAA28217@r...>

> The supposed problem with control characters in general is that the
> presence of those bytes in files causes problems.  I am suggesting
> that UTF-16 already gives us those problems.

They do, and I agree that UTF-16 has the same issues.

> But the specificproblem with nul is in XML APIs.  Any C API that uses
> nul-terminated strings will not be able to handle nuls in those
> strings.  If the strings are UTF-16 strings, they are terminated by a
> UTF-16 nul character, not by a single zero byte.  UTF-16 characters
> with zero bytes are not a problem.

XML parser/processor API's suffer the problem just as you say. Other non-XML 
aware programs/libraries will suffer similarly... that it what I was getting 
at.

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

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