> A preprocessing service is not a bad work around; and I > do have sympathy for the notion of standards of compliance. > Still, I see this problem (control characters) often enough > that I question the XML standard and Xerces' compliance to it. > XML Spy does not, though Microsoft's DOM parser does. Is > there any reason I can give my users other than that it is > verboten? Is there some good reason for these characters to > be off limits?
They are absolutely off-limits in XML 1.0, so any "pro-processing" you do will have to encode them in some application-specific way (base64 is often used). Whether or not there's a "good reason," I can't tell you, because I don't know the history, and "good" implies a value judgement I'm not willing to make. They are now allowed in XML 1.1, although they must be represented using numeric character references. However, XML 1.1 is a very recent recommendation, so finding tools that support it may be difficult. It's true that Microsoft's parser allows these characters, but it's non-standard behavior. If you really want to use XML, it's best to avoid relying on such non-standard behavior. Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
