RE: Subject: Re: Bug in treating an RTF by Saxon 6.5 a

> -----Original Message-----
> From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of Dimitre
> Novatchev
> Sent: Thursday, 16 May 2002 3:25 PM
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: Re: Subject: Re:  Bug in treating an RTF by Saxon 6.5 and
> MSXML 
> 
> 
> michael.h.kay@xxxxxxxxxxxx wrote:
> 
> > Dimitre Novatchev [dnovatchev@xxxxxxxxx], who should know better, 
> > claimed that MSXML4 and Saxon exhibit a bug in their handling of
> RTFs.
> > 
> > The quoted lines are all valid, as far as I can see, because $arg1 is
> > not an RTF. (I say "as far as I can see", because I haven't really 
> > worked out what arguments are being supplied to this template).
> 
> Yes, Dimitre Novatchev ***knows better*** -- the value passed in $arg1
> is an RTF.
> 
> 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


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