Subject: Re: last of type problem From: Jarle Stabell <jarle@xxxxxxxxxxxxx> Date: Fri, 15 Jan 1999 11:38:04 +0100 |
>regan@xxxxxxxxxxx wrote: >> > I have come across an issue that I >> initially thought would be easy: creating a comma separated list. ... James Clark wrote: >Not in general. Things are worse when the list is a result of sorting. >We know about this problem and it's on our list of issues. It needs to >be possible to do processing based on the position of the node not in >the source tree but in the list of nodes being processed with >xsl:for-each or xsl:apply-templates. When I generate text with code, I have methods with arguments similar to the following: Before, Item, Separator, After Where Before is the template/macro to invoke if the list is non-empty, Item is what to do with each item in the list, Separator is what to do between each Item, and After is processed if the list is non-empty (as Before). I'd love to see something similar in XSL. Cheers, Jarle Stabell XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: last of type problem, James Clark | Thread | Pattern matching, Bovone Stefano |
Re: GOTCHA!, Oren Ben-Kiki | Date | Re: GOTCHA!, James Clark |
Month |