This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: Subject: Re: Bug in treating an RTF by Saxon 6.5 and MSXML
- From: Joerg Heinicke <joerg dot heinicke at gmx dot de>
- To: xsl-list at lists dot mulberrytech dot com
- Date: Thu, 16 May 2002 20:37:56 +0200
- Subject: Re: Subject: Re: [xsl] Bug in treating an RTF by Saxon 6.5 and MSXML
- References: <LOBBICBLDJIJHPNJFPOLKEBGCGAA.mike@ammd.com.au>
- Reply-to: xsl-list at lists dot mulberrytech dot com
>>Here's the template with the offending lines again:
>>
>> <xsl:template match="str-split2words-func:*">
>> <xsl:param name="arg1" select="/.."/>
>
>
> <snip/>
>
> If the select attribute is used on a xsl:param, isn't the value of
> the parameter the result of the XPath expression, in which case its
> a boolean, a number, a string, or a nodeset? Its only an RTF is you
> include a template in the body of the xsl:param elements. So the
> correctness or otherwise of the later operations depends on what
> XPath expression you use.
>
> Regards
> Michael
Hello Michael,
the select-statement at <xsl:param/> is only for the default value of
the param. If you write something like:
<xsl:with-param name="arg1">
<test>constructing a RTF</test>
</xsl:with-param>
you pass a RTF to template.
Joerg
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list