Do a Google search on "XSLT" and "attribute value template".
--
Charles Knell
cknell(_at_)onebox(_dot_)com - email
-----Original Message-----
From: Jelks Cabaniss <jelks(_at_)jelks(_dot_)nu>
Sent: Tue, 29 Mar 2005 12:58:57 -0500
To: <xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com>
Subject: [xsl] param weirdness
This *should be* obvious, but sometimes the obvious isn't always to this
observer. :)
<xsl:call-template name="detail">
<xsl:with-param name="category">markup</xsl:with-param>
</xsl:call-template>
..
<xsl:template name="detail">
<xsl:param name="category" />
<xsl:for-each select='/config/option[(_at_)class="$category"]'>
...
</xsl:for-each>
</xsl:template>
The for-each selects *nothing*, but if I change "$category" to the
hard-coded string "markup", it works fine!
The `$category` parameter does come through, or so
<xsl:value-of select='$category' />
tells me. So why does does a hard-coded category work, while "$category"
fails?
/Jelks
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--