[EMAIL PROTECTED] wrote:
Hi all,Yes, It would be good to pass that information. Right now encoding information about the external dtd subset is not passed at all. I was thinking, does any of the existing standards SAX/DOM requires it ?
How does one determine the autodetected encoding of a DTD external subset?
Right now, our DTD scanner takes this information from the entity manager in a (non-XNI) startEntity(name, resourceIdentifier, encoding) call but drops the encoding information on the floor for entities whose names are [dtd].
It sure would have been handy if the
XMLDTDHandler#startExternalSubset(XMLResourceIdentifier, Augmentations) had
also included an encoding parameter...
I was also thinking that XNI "XMLLocator" interface doesn't have encoding information, it would be nice to have this interface having encoding detail considering the fact that XNI uses it for instance document & DTD. It would allow to know the encoding information about the current entity being parsed at any point of time. Currently to determine the encoding of the instance document user would have to do it using startDocument() and xmlDecl() calls.
Neeraj
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
