Title: contradictory encoding warning creates later error that doesn't get thrown

Hi,

I'm having a problem when there are SAX parser warnings.  It appears that processing continues in the case where the encoding scheme mentioned in a document is not its true encoding.  The SAX parser does throw a warning to my error handler, but then continues to attempt to parse with a NULL encoding string value which causes an access violation error. 

First, shouldn't a contradictory encoding be an "error" rather than a mere "warning"?  Second, if these are considered mere warnings, then how do I get processing to halt after a contradictory encoding has been discovered?

Siehnai Williamson
DocuCorp International, Inc.

Reply via email to