This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: generate xsl 1.0 from 2.0 question
- From: "Bryan Rasmussen" <bry at itnisk dot com>
- To: <xsl-list at lists dot mulberrytech dot com>
- Date: Wed, 23 Jan 2002 12:11:23 +0100
- Subject: RE: [xsl] generate xsl 1.0 from 2.0 question
- Keywords: xsltDEV
- Reply-to: xsl-list at lists dot mulberrytech dot com
thanks jeni, I came to sort of the same conclusion(our posts crossed), post
starts with line about coffee kicking in.
><xsl:template name="createChoose">
><xsl:param name="translatorName" />
> <temp:choose>
> <xsl:for-each select="$translator[@name = $translatorName]
> /(* | processing-instruction())">
> <xsl:call-template name="translator" />
> </xsl:for-each>
> </temp:choose>
></xsl:template>
>[Note that I've swapped the child::node()[name() != ''] for something>
>that explicitly selects the nodes that have names (i.e. elements and
>processing instructions) using XPath 2.0 general steps. I suspect that
>you're just after the elements, in which case you could just use
>$translator[@name = $translatorName]/*.]
yep I was just after the elements. :) thanks again.
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list