I don't think you'd find it worth the effort. The core parser bits are very heavily tied directly to the XML format. There is no reason for it to do otherwise really, since it's an XML parser. You could obviously slip your own parsing system underneath a SAX or DOM API, since they are pretty well separated (and as long as it's just the syntax and not the substance that is different, i.e. you still spit out XML infoset data just parsed from a different format), but the parsing parts probably would be more trouble to try to rework than it's worth, depending on how different your alternate encodings are.
That's my guess anyway. ------------------------------------- Dean Roddey The Charmed Quark Controller [EMAIL PROTECTED] www.charmedquark.com -----Original Message----- From: Tahir Hashmi [mailto:[EMAIL PROTECTED] Sent: Thursday, March 06, 2003 10:28 PM To: [EMAIL PROTECTED] Subject: Making Xerces parse other formats Hi! I'm working on alternate encodings of XML and one of my objectives is compatibility with XML API and processing. I'd like to have Xerces be able to recognize and parse the alternate format too, so that I may have a working demo available. I'd like to know whether the XML parsing and generation classes are cleanly separated from the higher layers (e.g. SAX/DOM interface implementations) and if they are, then which classes or interfaces I should re-implement. Thanks in advance. -- Tahir Hashmi (VSE, NCST) http://staff.ncst.ernet.in/tahir tahir AT ncst DOT ernet DOT in We, the rest of humanity, wish GNU luck and Godspeed --------------------------------------------------------------------- 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]
