This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: Boolean expr in <xsl:when>
- From: "Schmoll, Brett x66244" <BSchmoll at bis dot adp dot com>
- To: "'xsl-list at lists dot mulberrytech dot com'" <xsl-list at lists dot mulberrytech dot com>
- Date: Fri, 22 Feb 2002 12:00:07 -0500
- Subject: RE: [xsl] Boolean expr in <xsl:when>
- Reply-to: xsl-list at lists dot mulberrytech dot com
Personally I don't have any problem upgrading to MSXML3 or 4. It's those
darn "users" that are the problem. The transform occurs client-side and I am
limited to IE 5.5 sp2 as the minimum browser requirement.
At least the XSLT is correct, I thought that was how it should work. So plan
B appears to be nesting multiple <xsl:choose> elements to test each
condition.
Thanks!
-Brett Schmoll
ADP/SIS
-----Original Message-----
From: David Carlisle [mailto:davidc@nag.co.uk]
Sent: Friday, February 22, 2002 9:27 AM
To: xsl-list@lists.mulberrytech.com
Subject: Re: [xsl] Boolean expr in <xsl:when>
> How do I test for multiple conditions in a xsl:when element? e.g.
<xsl:when
> test="*/foo[.='a'] and */bar[.='b']">
that is correct XSLT.
> My problem may be that I'm using MSXML 2.6.
That doesn't implement XSLT but an entirely different language, so XSLT
expressions don't work. Why can't you upgrade tp MSXML 3 or 4 ?
David
_____________________________________________________________________
This message has been checked for all known viruses by Star Internet
delivered through the MessageLabs Virus Scanning Service. For further
information visit http://www.star.net.uk/stats.asp or alternatively call
Star Internet for details on the Virus Scanning Service.
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list