Vladimir,
At 04:10 AM 6/15/2010, you wrote:
I agree that there are ways to workaround the problem.
At present I'm inclined to use approach similar to Liam's Method (1).
I'm just wondering if I'm missing something, if there is a simple
solution?
At heart, the problem you are having is that you need a syntax in
your results that breaks the rules of XML well-formedness, so the XML
serializer that comes with your processor won't work unassisted.
David's suggestion of using d-o-e, or for that matter the idea of
reserving a character and using a character map, are both ways of
contriving workarounds to allow you to do this.
Two other options would be to (a) write your own result serializer,
assuming your processor allows you to use it, which could for example
pick up elements in a namespace and do the right thing with them, and
(b) use the "text" output method in an XSLT post-process that
serializes both the XML and the non-XML syntax the way you want it.
While it's kind of bizarre to write an XML serializer in XSLT, it has
been done.
But Liam's recommendation to run a post-process outside XSLT
altogether may be simplest. And they all amount to the same thing.
Cheers,
Wendell
======================================================================
Wendell Piez
mailto:wapiez(_at_)mulberrytech(_dot_)com
Mulberry Technologies, Inc. http://www.mulberrytech.com
17 West Jefferson Street Direct Phone: 301/315-9635
Suite 207 Phone: 301/315-9631
Rockville, MD 20850 Fax: 301/315-8285
----------------------------------------------------------------------
Mulberry Technologies: A Consultancy Specializing in SGML and XML
======================================================================
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--