Ditto the other answers. The whole point of a strict standard is that you know that the documents you have (once they go through a compliant parser) should go through any compliant parser. HTML turned into a race to the bottom and this browser couldn't parse that page but the person creating that page says, "But it works for me." XML cannot allow that because not only is it for visual markup, where a failure to comply is a visual annoyance, it's for semantic information and data, which will cause far greater failures. It would make the world a very muddled, confused place, where evil doers can create confusion and despair.
------------------------------------- Dean Roddey The Charmed Quark Controller [EMAIL PROTECTED] www.charmedquark.com -----Original Message----- From: Marc Seldin [mailto:[EMAIL PROTECTED] Sent: Thursday, September 23, 2004 8:18 AM To: [EMAIL PROTECTED] Subject: Making Xerces less strict? While in theory it makes good sense to have a strict parser, in the world of my clients getting them to make generally well formed documents is difficult enough. I've been getting a number of complaints about the "invalid character" error; usually they've included some control character, like an ASCII 18. (http://xml.apache.org/xerces-c/faq-parse.html#faq-20) Is there any way to make the xerces parser less strict? If not, I'd like to put in a feature request for this. It would really make the world a happier, shinier place. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
