Lists Home |
Date Index |
- From: David Brownell <db@Eng.Sun.COM>
- To: Miles Sabin <firstname.lastname@example.org>
- Date: Wed, 03 Mar 1999 13:57:45 -0800
Miles Sabin wrote:
> David Brownell wrote,
> > "Richard L. Goerwitz" wrote:
> > > David Brownell wrote:
> > > > And more to the point, XML processors aren't
> > > > required to report such low level character
> > > > encoding errors ... this would be one.
> > >
> > > On the face of things, this doesn't make sense.
> > For example, character encodings are typically handled
> > many layers below the XML processor. That processor
> > shouldn't be faulted for behaviors of the underlying
> > processor.
> Most of the time yes ... but remember we're discussing
> the interaction between encoding detection and encoding
> _declarations_. An XML processor has to have some
> involvement in that.
But the error in question would show up after the encoding
declaration had been processed -- well after! -- so the
XML processor itself would no longer need involvement.
The non-normative "detection" can't involve the error ...
surrogates can't appear within encoding declarations.
In any case, it's OK for conformant processors to reject
UCS-2 out of hand, eliminating all possibility of such
an error in any case!
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)