Subject: [xsl] Re: Creating a XSL to return the input From: "Dimitre Novatchev" <dnovatchev@xxxxxxxxx> Date: Tue, 4 Mar 2003 22:45:16 +0100 |
> 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 > behave differently: > > 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 transformation". 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... ===== Cheers, Dimitre Novatchev. http://fxsl.sourceforge.net/ -- the home of FXSL XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] Re: Creating a XSL to ret, Daniel Veillard | Thread | Re: [xsl] Re: Creating a XSL to ret, Daniel Veillard |
Re: [xsl] Re: Creating a XSL to ret, David Carlisle | Date | Re: [xsl] Re: Creating a XSL to ret, Daniel Veillard |
Month |