Re: [xsl] Handling Tree Fragments

Subject: Re: [xsl] Handling Tree Fragments
From: Gustave Stresen-Reuter <tedmasterweb@xxxxxxx>
Date: Mon, 26 Sep 2005 18:33:17 +0100
Thanks for the reply. I'm sorry, but I'm really a dunce... I had the exslt extension working for some files but I've since lost them. Can you give me an example (including how to set the namespace and such)?

Also, I tried the document() method, but, since the variables are actually generated (and not just static XML), it returns the XSL used to generate the variables.

Thanks again.


On Sep 26, 2005, at 4:30 PM, andrew welch wrote:

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:apply-templates select="document('')//xsl:variable[@name = RTF]"/>

On 9/26/05, Gustave Stresen-Reuter <tedmasterweb@xxxxxxx> wrote:

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 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