I have learned that XSLT officially acts on an entity-free parse tree, but for me this is a very inconvenient and annoying misfeature. The SAX API includes a way of passing unrecognised entities along the pipeline: the skippedEntities call. Is there a way of persuading Cocoon2, and Xalan, to treat this event just like a text node event, and thus preserving unrecognised entities in the output stream?
I nearly have my Cocoon-based website creation working, but I've just hit the problem that it chokes on pages containing HTML entities and from what I can see any way of fixing the problem is a huge job, which seems very unfair... Many thanks, -- __ Paul Crowley \/ o\ [EMAIL PROTECTED] /\__/ Employ me! http://www.cluefactory.org.uk/paul/cv/ Cryptography, Linux, Unix, Perl, C/C++, Java, TCP/IP, and more. --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
