This is the mail archive of the xsl-list@mulberrytech.com mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: generate xsl 1.0 from 2.0 question


now the coffee's kicking in, I should be able to get rid of all my named
templates, click_here etc. and just have
<xsl:template name="translator2">
<xsl:param name="transparam"/>
<temp:choose><xsl:for-each
select="$translator[@name=$transparam]/child::node()[name()!='']">
<xsl:call-template name="translator"/></xsl:for-each></temp:choose>
</xsl:template>
right? in xslt 2.0 I mean. Is there any optimization that can be done on
that?

>anyway the thing I was wondering about is in the template name="click_here"
>you'll notice I do the $translator[@name='Click_here'] is there anyway to
>select the name of the template one is in(in xslt 2.0), in such a way that
I
>could make a parameter holding the template/@name value and pass it to a
>named template through a call?





 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list



 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]