Edward Rayl wrote: > Think we might need a "Parse > as HTML" option, or catch the XML exception and then automatically > parse through jtidy?
I was thinking of simply using JTidy for both HTML and XHTML so we avoid this problem altogether. I'll check if JTidy handles XHTML parsing correctly. It should leave the tree structure intact, provided the page was well-formed and valid to begin with. -Laurens _______________________________________________ plucker-list mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-list
