You could try using the NekoHTML parser (based on Xerces) and feeding its output to Xalan for XSLT processing. I don't think we have a canned off-the-shelf demonstration of that combination, but it ought to be straightforward.
I believe the W3C's "tidy" tool can also be persuaded to function as an HTML parser rather than doing its full parse-and-regenerate cycle. ______________________________________ "... Three things are most perilous: Connectors that corrode, Unproven algorithms, and self-modifying code! ..." -- "Threes" Rev 1.1 - Duane Elms / Leslie Fish (http://www.ovff.org/pegasus/songs/threes-rev-11.html) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
