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

Re: Some comments on the 1.1 draft

• To: <xml-dev@l...>
• Subject: Re: Some comments on the 1.1 draft
• From: "Rick Jelliffe" <ricko@a...>
• Date: Fri, 21 Dec 2001 18:16:14 +1100
• References: <E16GeCZ-0004ll-00@m...>

From: "John Cowan" <cowan@m...>
 
> Rick Jelliffe scripsit:
> 
> > Even if you only use ISO 8859-1, it is still important. The Euro=0x80
> > mistake will be increasingly common, and we need to make sure that
> > XML processors continue to catch this error.
> 
> But they don't!
> 
> Characters U+0080 through U+009F are legal XML content.
> 
> You are talking about a "defense" that doesn't even exist.
 
No. 0x0085 is not AFAIK a character in ISO 8859-1 (it is one of the design principles
of 8859-1 that it will not fail on systems that mask the 8th bit and look for control
characters).   So a document labelled as ISO 8859-1 but with an 0x85 false Euro
should fail on import. The 85 character not existing in 8859-1, it never gets as far
as Unicode.

MSXML 4 gets this right, and gives an error at those times. I have had a support
request on this with our validator, so I had to look into it.

The defense does exist.

Cheers
Rick Jelliffe

• Follow-Ups:
  • Re: Some comments on the 1.1 draft
    • From: John Cowan <jcowan@r...>

• References:
  • Re: Some comments on the 1.1 draft
    • From: John Cowan <cowan@m...>

• Prev by Date: Re: Why would MS want to make XML break on UNIX, Perl, Python, etc ?
• Next by Date: Re: Recently published W3C Working Drafts (long)
• Previous by thread: Re: Some comments on the 1.1 draft
• Next by thread: Re: Some comments on the 1.1 draft
• Index(es):
  • Date
  • Thread