|
[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: Possible changes for XML 2nd Edition
On Wed, 24 May 2000 14:51:43 -0400, you wrote: >Currently the XML Recommendation is silent about the handling of >documents that contain "impossible" bytes. For example, the byte 0xFF >cannot appear in any UTF-8 encoded document. We are considering making >such violations of the encoding a fatal error. The way I handle it now is to try to determine the encoding using the Appendix F heuristics (or the explicit encoding declaration, if it exists), and then switch to a stream that understands that encoding and spits out Unicode characters. If that stream subsequently encounters such an "impossible" byte, then it throws an exception. The parser per se never gets to see it. >CON: Some parsers may be relying on libraries supplied by the OS, which may >not properly signal erroneous input. Is it too great a burden on the >parser implementor to impose this restriction? I don't see this as a significant issue. If I find that a library function that I'm using is silently swallowing errors of this magnitude, then I'm going to dump the library function and use something else. -Steve Schafer *************************************************************************** This is xml-dev, the mailing list for XML developers. To unsubscribe, mailto:majordomo@x...&BODY=unsubscribe%20xml-dev List archives are available at http://xml.org/archives/xml-dev/ ***************************************************************************
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|
|||||||||

Cart








