This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: Another XSL question
- From: "cutlass" <cutlass at secure0 dot com>
- To: <xsl-list at lists dot mulberrytech dot com>
- Date: Wed, 24 Apr 2002 17:30:34 +0100
- Subject: Re: [xsl] Another XSL question
- References: <F269QkPclN70dihnCB70001278c@hotmail.com>
- Reply-to: xsl-list at lists dot mulberrytech dot com
Hello Manoj,
----- Original Message -----
From: "Manoj Jha" <manoj_k_jha@hotmail.com>
> <xsl:template match="DocumentDetails/*[. = 'CLOSING CONDITIONS:']">
> <!-- do some transformation by adding new condition text nodes such
> that remaining condition text nodes get incremented based on the
> introduction of these new nodes -->
> </xsl:template>
hmm, u do have a rather fundamental non-awareness of the processing model
that is present within xslt.
essentially what u want to do is apply a transformation, then apply another
transformation to that result, correct me if i am wrong ( i think i am going
blind reading other peoples xslt ! ).
a) place the results of a transform either in a file and access with
document() call
or
b) place result nodeset in a variable
<xsl:variable name="process1">
do something here....... ( apply-templates....i would have named or moded
templates )
</xsl:variable>
now u have a var called $process1 to do stuff with , but there is still a
small problem, its not a 'real' nodeset, so you have to convert it using the
common extension function called node-set() which converts the RTF into a
node for processing.
now apply templates to this result
<xsl:apply-templates select="msxsl:node-set($process1)"/>
this is an example using M$ processor.
i would suggest reviewing the FAQ at www.dpawson.co.uk you will get some
fundamental stuff there.
gl, jim
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list