[XSL-LIST Mailing List Archive Home] [By Thread] [By Date]

RE: The XSL-List Digest V2 #488


Subject: RE: The XSL-List Digest V2 #488
From: Philip Borenstein <pb@xxxxxxxxxx>
Date: Thu, 27 Jan 2000 16:59:50 -0500

Thanks. That did the trick.
I keep trying to solve most of my problems iteratively (and lately
recursively)
but it seems that the answer is always some concise path expression. Every
time I see "[ ... ]" I keep thinking it's an array.

> -----Original Message-----
> From:	Mike Brown [SMTP:mbrown@xxxxxxxxxxxxx]
> Sent:	Thursday, January 27, 2000 4:36 PM
> To:	'xsl-list@xxxxxxxxxxxxxxxx'
> Cc:	'pb@xxxxxxxxxx'
> Subject:	RE: The XSL-List Digest V2 #488
> 
> > >    <xsl:if at-at-least-one-TASK-has-a-non-empty-DESCRIPTION>
> > <xsl:if test="string(DESCRIPTION)">
> 
> Oh, sorry, I missed the "if at-least-one ..."
> What I gave you was "if this TASK ..."
> Try this:
> 
> <xsl:if test="../TASK[string(DESCRIPTION)]">
> 
> It will be true if this node-set is not empty:
> 
> child elements of the parent node of the current node
>  that are named TASK
>  and for which this is true:
>    there is a not-null string value of the
>    DESCRIPTION child element of the current node


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



Current Thread