Subject: Re: [xsl] position of arbitrary parent From: Laurence O Garfield <lgarfiel@xxxxxxxxxxxxxxxxxxx> Date: Tue, 17 Jul 2001 13:25:21 -0500 (CDT) |
On Tue, 17 Jul 2001, David Carlisle wrote: > > > which leaves me back with needing to know the > > position() of the current <chapter> element. > > > Probably you need to pass the chapter node as a parameter down to you > html templates. > > <xsl:for-each select="chapter"> > <xsl:apply-templates select="$chapterTemplate/html" > > <xsl:with-param name="c" select="."/> > <xsl:apply-templates/> > </xsl:for-each> > > and then declare c param in your templates that handle your html doc, > > David That's what I was thinking, but that's going to get exceedinly ugly very fast. Would it be possible to use a globally defined variable that is edited just prior to the apply-templates call? Or are global variables non-editable? XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] position of arbitrary par, David Carlisle | Thread | Re: [xsl] position of arbitrary par, David Carlisle |
Re: [xsl] position of arbitrary par, David Carlisle | Date | Re: [xsl] position of arbitrary par, David Carlisle |
Month |