[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: output a literal CDATA section
Georges,
What you've said below suggests to me that I was correct in guessing that you could use verbatim tag-writing to get the "inner" XML (not to be parsed) inside your "outer" XML (the Docbook, which must work as Docbook). On the other hand, if you're already doing it cleanly with a post-process to escape those tag structures you don't want parsed (by wrapping them in CDATA section delimiters) -- that should be okay too. As long as you're happy with the soundness of the post-process. As Mike indicated, I think, the trickiness here stems from the fact that XSLT works on node structures, not on tags, and relies on a serializer to turn the result tree into tagged text (i.e. XML as we know it). This means there's an "all or nothing" aspect to it. Once one internalizes how tagging that's wrapped as CDATA in an XML file isn't actually tagging at all -- it's just data, which just happens to have "tags" in it -- it becomes clearer why one can't generate it by the usual means (building a tree and then letting the serializer write it out). Hence special approaches such as verbatim tag-writing techniques, or supplementary non-XML-aware approaches that work directly on the tags-in-text rather than on the tree that an XSLT processor would build. Cheers, Wendell At 11:58 AM 7/21/2005, you wrote: we need a documentation (I got the developers to accept DocBook as format) of an import/export interface in xml, where data is mapped in java objects. The import interface is in draft state, so there will be changes in future to the structure, as well as to the example values contained in the tags.
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|