This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: testing for several different conditions
- To: "'XSL-List at mulberrytech dot com'" <XSL-List at mulberrytech dot com>
- Subject: Re: testing for several different conditions
- From: Eric Taylor <Eric dot Taylor at RealPage dot com>
- Date: Fri, 29 Sep 2000 07:30:13 -0500
- Cc: "'NickBrowne at slipstone dot co dot uk'" <NickBrowne at slipstone dot co dot uk>
- Reply-To: xsl-list at mulberrytech dot com
Nick, thanks much. This did the trick. I appreciate your taking the
trouble to dig through old books on my behalf!
I agree with the arguments for upgrading--I'd much prefer to--but right now
corporate policy dictates that for this project we produce something that
will transform for users with IE5 as shipped, so until they generally
release an XSLT compliant browser, I'm stuck... For other stuff that I can
transform in house, I am starting to use real XSLT with Instant Saxon.
And Andrew, thanks for the pointer to the vbxml list on egroups.com for
further help with this obsolete stuff.
Eric
> From: Nick Browne <NickBrowne@slipstone.co.uk>
> Subject: Re: testing for several different conditions
>
> Eric, having looked through some 'old' books I think the problem is that
early
> versions of MSXML only allow boolean operators inside a predicate. One
even
> showed the syntax of xsl:if to use a 'match' attribute in place of 'test',
> suggesting that only a valid path was/is allowed.
>
> If you change your line to :
>
> <xsl:if test= ".[(//bookmark/@name = @internal) $or$ (@internal =
> 'whatnext' $and$ //next)]">
>
> ...The advice to upgrade is probably the best though I appreciate this may
not be
> practical given restrictions on your environment.
>
> Regards
> Nick Browne
> Slipstone Ltd
>
> Eric Taylor wrote:
>
> > ... Here's the offending line:
> >
> > <xsl:when test= "(.[//bookmark/@name = @internal]) $or$ (.[@internal
=
> > 'whatnext'] $and$ //next)">
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list