At 06:37 PM 3/13/2003, Mike wrote:
Alright, I guess I can try to help, under the assumption that you're trying
to generate CFML with XSLT.
[stuff cut about CFML's particular syntax not being XML]
...
This may be a case for the use of disable-output-escaping, where you write
all your tags as XML character data and then tell the serializer to emit them
without escaping the markup characters "<" and "&":
...
but this kludgy "solution" is not guaranteed to work at all (its support is
optional and relies on the processor serializing the result tree directly).
See also http://www.dpawson.co.uk/xsl/sect2/N2215.html
A variation of this approach is to use the "text" output method, in which
output is escaped by default, and use named templates to generate your CFML
tags (appropriately parameterized so they can be called from your
processing templates).
Just a thought, a variation on Mike's theme. Post-processing XML output, as
Mike also suggested, is another option: it amounts to splitting the problem
in half and isolating the problematic issue (getting non-XML markup output)
for a non-XSLT tool to deal with (easy as a regexp-based process may be in
this case).
Cheers,
Wendell
___&&__&_&___&_&__&&&__&_&__&__&&____&&_&___&__&_&&_____&__&__&&_____&_&&_
"Thus I make my own use of the telegraph, without consulting
the directors, like the sparrows, which I perceive use it
extensively for a perch." -- Thoreau
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list