[XSL-LIST Mailing List Archive Home]
[By Thread]
[By Date]
David Carlisle wrote:
Right.
Well, I'm not going to do that. The whole point (in my use case) is to be able to serve the XML source, and let the UA transform it.
Or, alternatively, if all the "other" XSLT 1.0 engines implemented msxsl:node-set. Just mentioning that for the sake of completeness :-).
Best regards, Julian
Re: [xsl] XSLT and XML in the same document
Subject: Re: [xsl] XSLT and XML in the same document From: Julian Reschke <julian.reschke@xxxxxx> Date: Tue, 29 May 2007 14:20:36 +0200 |
David Carlisle wrote:
if you are calling the stylesheet from <?xml-stylesheet it seems that the pain can't be avoided (the trick of using msxsl:script to define exslt:node-set doesn't seem to work unfortunately, and the trick of using exslt:function to define msxsl;node-set would only work if the other browsers implemented exslt:function)
Right.
However if you are calling the transform from the javascript API, one alternative to complicating the xslt with lots of nested function-available tests is simply to modify the source (Or DOM) of the stylesheet to use the MS namespace rather than the EXSLT one before compiling the stylesheet.
Well, I'm not going to do that. The whole point (in my use case) is to be able to serve the XML source, and let the UA transform it.
Of course even more pain would go away if they were to implement xslt2 as you wouldn't need node-set() at all!
Or, alternatively, if all the "other" XSLT 1.0 engines implemented msxsl:node-set. Just mentioning that for the sake of completeness :-).
Best regards, Julian
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] XSLT and XML in the same , David Carlisle | Thread | Re: [xsl] XSLT and XML in the same , David Carlisle |
Re: [xsl] XSLT and XML in the same , Julian Reschke | Date | Re: [xsl] XSLT and XML in the same , Julian Reschke |
Month |