Thanks Ken.
Because all the variables I had constructed using the select="some text"
idiom seemed to have no value when accessed, I adopted the text node
approach. I'll go back and look at my old code now to see if there was
another reason for the value-setting failure.
Mark
-----Original Message-----
From: G. Ken Holman
Sent: Monday, October 03, 2011 2:26 PM
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: Re: [xsl] Providing a value for the 'select' attribute
At 2011-10-03 14:19 -0700, Mark wrote:
I have been using the following idiom when providing a value for
“select†in statements like <xsl:param>, <xsl:variable>, etc., when the
value provided is not an xsl object. Is this correct or is some other form
preferred?
<xsl:param name="file-type">
<xsl:text>.htm</xsl:text>
</xsl:param>
The above is a text node, as is this:
<xsl:param name="file-type">.htm</xsl:param>
This is slightly different in that it is a string:
<xsl:param name="file-type" select="'.htm'"/>
But for your use that difference is nuanced based
only on how the item is stored in memory.
I hope this helps.
. . . . . . Ken
--
Contact us for world-wide XML consulting and instructor-led training
Crane Softwrights Ltd. http://www.CraneSoftwrights.com/s/
G. Ken Holman mailto:gkholman(_at_)CraneSoftwrights(_dot_)com
Google+ profile: https://plus.google.com/116832879756988317389/about
Legal business disclaimers: http://www.CraneSoftwrights.com/legal
--~------------------------------------------------------------------
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>
--~--