Subject: Re: [xsl] Handling Tree Fragments From: andrew welch <andrew.j.welch@xxxxxxxxx> Date: Mon, 26 Sep 2005 16:30:54 +0100 |
Use the node-set extension function for your processor - or if it supports exslt common then use that for the extra portability. Other than that you could use function-available and a choose-when to choose the correct node-set extension for the main big players, but that's a bit tiresome. The other way is to use document('') to return the stylesheet itself eg: <xsl:variable name="RTF"> some constructed nodes </xsl:variable> and: <xsl:apply-templates select="document('')//xsl:variable[@name = RTF]"/> On 9/26/05, Gustave Stresen-Reuter <tedmasterweb@xxxxxxx> wrote: > Hi, > > I'm wondering if someone can point out how to use tree fragments as > node sets in XSLT 1.0. Some processors (Saxon) seem to handle tree > fragments without any additional work but others (Sablotron and > libxslt) don't seem to like them very much. > > I've read the documentation on exslt.org and tried to implement the > conversion of tree fragments to node sets using their documentation, > but I just cannot get it to work (complains about not being able to > find the imported file). > > Ideally, I'd like to avoid using extensions altogether, but I realize > that that may be impossible. > > Any ideas? > > Ted Stresen-Reuter
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
[xsl] Handling Tree Fragments, Gustave Stresen-Reut | Thread | Re: [xsl] Handling Tree Fragments, Gustave Stresen-Reut |
RE: [xsl] Need help using variable , Michael Kay | Date | Re: [xsl] Strict sequential identit, Wendell Piez |
Month |