[EMAIL PROTECTED] wrote:
> First, Xerces 1.4.1 does support UTF-16. If you have a UTF-16
> document that it isn't recognizing, I'd love to see it.
It doesn't support it in the simple sense that if I specify UTF-16 as
the encoding, the parser throws an exception:
SLDBGenComp/SAXParser exception:
src/de/step/SLMADB/SLDBGenComp/xml/def0000.xml:-28: The encoding
"UTF-16" is not supported.
> Second, the problem you're having with characters is probably caused
> by the fact that Xerces may return multiple character callbacks for
> a single piece of character content. The SAX spec explicitly allows
> implementations to do this--to avoid buffering problems--and Xerces
> takes advantage of this flexibility.
The documentation to HandlerBase.characters doesn't say this, but I
see that it is now deprecated. I suppose I can program around this,
but it seems to me that something was fixed that wasn't broken...
> I have no idea about the locator problem. I think Xerces generally
> does a fair job of reporting the locations of problems in instance
> documents, but it's certainly true that it doesn't always for
> grammars. This is only my perception however and I'd be interested
> to hear your experiences.
Maybe I have to upgrade to non-deprecated classes. This actually looks
pretty complicated. Is there a document with hints about how to do
this?
Thanks Neil!
David
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
