as you can see in the comments the output method has been set to text
so that < and > would be treated properly. Elsewhere I have read
that this is not a recommended way of creating an output XML.
You do lose most (or at least many) of the benefits of XSL if you do
this. The point of XSLT is that it consists of "templates" that are fragments
of the output tree, but in your case you are not constructing a tree at
all, just a flat string that happens to have some , and > in.
I thought it would be possible to use <xsl:copy-of select="."/> in the
two template match functions at the bottom, but it did not work
correctly.
that would copy all the nodes from the source, but as you have asked for
text output, you onlyget text nodes serialised, all element and
attribute nodes are discarded.
It's probably not a good style to post complete source code examples,
On the contray, it's _much_ easier to answer questions of the form
test input - test style - test result - required resulut.
than to answer questions with a vague description of a possible problem
in some unspecified program. (We get a lots of both sorts of question on
this list:-)
Basically you want an identity transform with some modified templates,
the FAQ has an example here
http://www.dpawson.co.uk/xsl/sect2/identity.html#d4096e43
How complicated are your parameters $filterstmt, if they are not
complicated you may be able to do without using the evaluate()
extension function as well.
David
________________________________________________________________________
This e-mail has been scanned for all viruses by Star Internet. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list