W3C home > Mailing lists > Public > www-xsl-fo@w3.org > May 2008

Sanitizing data

From: JohnVirgo <john.virgo@document.co.uk>
Date: Tue, 6 May 2008 03:43:23 -0700 (PDT)
Message-ID: <17080137.post@talk.nabble.com>
To: www-xsl-fo@w3.org


I've got an interesting problem that I'm hoping to solve with XSLT.

Basically I have an XML document inbound which could contain additional
nodes that I do not currently handle in my XSL template; or worst still a
node with multiple child nodes of which I am only expecting a single child
node.

Can anyone give any pointers on the easiest way to trap and identify the
additional data in the source XML that my template does not handle?

I've considered:
* Using XSL debugging commands to throw exceptions, but how to identify
them?
* Pumping out all un-processed data to a single text block at the end of the
FO for visibility. But how can identify un-processed nodes?
* Pre-parse the xml with another XSLT, kind of redundant/not ideal

Thanks, JV
-- 
View this message in context: http://www.nabble.com/Sanitizing-data-tp17080137p17080137.html
Sent from the w3.org - www-xsl-fo mailing list archive at Nabble.com.
Received on Tuesday, 6 May 2008 10:43:59 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 6 May 2008 10:43:59 GMT