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: "Michael Leditschke" <mike at ammd dot com dot au>
- To: <xsl-list at lists dot mulberrytech dot com>
- Date: Thu, 16 May 2002 16:41:21 +1000
- Subject: RE: Subject: Re: [xsl] Bug in treating an RTF by Saxon 6.5 and MSXML
- Reply-to: xsl-list at lists dot mulberrytech dot com
> -----Original Message-----
> From: owner-xsl-list@lists.mulberrytech.com
> [mailto:owner-xsl-list@lists.mulberrytech.com]On Behalf Of Dimitre
> Novatchev
> Sent: Thursday, 16 May 2002 3:25 PM
> To: xsl-list@lists.mulberrytech.com
> Subject: Re: Subject: Re: [xsl] Bug in treating an RTF by Saxon 6.5 and
> MSXML
>
>
> michael.h.kay@ntlworld.com wrote:
>
> > Dimitre Novatchev [dnovatchev@yahoo.com], 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