don't forget that it was something just like this that provoked
my original posting about what match=node() really meant, and i'm
still wading through the responses, trying to summarize them.
in a nutshell, if you use that transform, xsltproc and saxon
saxon will copy over comments and processing instructions,
xsltproc will not
so, remind me again -- which one is behaving correctly?
This is not so difficult even to guess -- once you know that this is the
Identity is identity -- it must copy everything.
It seems to me that an XSLT processor that does not perform correctly the
identity transform (no offense, but this is difficult to believe)
demonstrates a complete lack of any testing...
http://fxsl.sourceforge.net/ -- the home of FXSL
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list