• From: Jeff Greif <jgreif@a...>
• To: Joshua Allen <joshuaa@m...>,Anoop A V <anoop_scorpio@h...>, xml-dev@l...
• Date: Tue, 23 Oct 2001 14:03:54 -0700

If the spec says it should be fatal, I agree, it should be treated as such.
It's also pretty easy to stream the text through an illegal-character filter
(on Unix or with cygwin installed on Win32, use the tr program) on the way
into the XML parser,
Jeff
----- Original Message -----
From: "Joshua Allen" <joshuaa@m...>
To: "Jeff Greif" <jgreif@a...>; "Anoop A V"
<anoop_scorpio@h...>; <xml-dev@l...>
Sent: Tuesday, October 23, 2001 1:17 PM
Subject: RE:  To continue parsing after a fatal error.


Actually, the invalid character error is per the XML 1.0 spec fatal.  If
Microsoft were to deviate from the W3C spec and make this ignorable, we
would deserve the roasting we would get at the merciless hands of
xml-dev list members.  The reasoning behind the rule is that it prevents
the spread of malformed XML, and thereby preserves interoperability.
This is a good and necessary reason, although it is not much consolation
when you are stuck trying to clean up bad XML.  We should have some
tools to make this easier..

• References:
  • RE: To continue parsing after a fatal error.
    • From: Joshua Allen <joshuaa@m...>

• Prev by Date: RE: To continue parsing after a fatal error.
• Next by Date: Who can implement W3C XML Schema ?
• Previous by thread: RE: To continue parsing after a fatal error.
• Next by thread: Re: To continue parsing after a fatal error.
• Index(es):
  • Date
  • Thread