Re: looping problem, <xsl: for-each>??

Hi Wendell,
  I was able to generate numbering 1,2,3,4.. 

I applied your suggestion to store an intermediate
tree fragment in a variable, and then converting the
variable into a nodeset. By iterating the nodeset, I
am able to generate numbers 1,2,3,4.. 

The XSL is --

<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:xalan="http://xml.apache.org/xalan">
<xsl:output method="xml" version="1.0"
encoding="UTF-8" indent="yes"/>

<xsl:key name="x" match="/rss/channel/item"
use="category"/>
<xsl:template match="/">
  <xsl:variable name="treeFrag">
    <rootelem>
      <xsl:for-each select="rss/channel/item">
	<xsl:if test="generate-id(.) = generate-id(key('x',
category)[1])">
	  <h1>						    <xsl:value-of select="category"/>
	  </h1>
	  <xsl:for-each select="key('x', category)">
	    <desc>
	      <xsl:value-of select="description"/>
	    </desc>
          </xsl:for-each>
        </xsl:if>
      </xsl:for-each>
    </rootelem>
  </xsl:variable>
		
  <xsl:for-each
select="xalan:nodeset($treeFrag)/rootelem/desc">
    <xsl:if test="name(preceding-sibling::*[1]) =
'h1'">
      <h1>
	<xsl:value-of select="preceding-sibling::*[1]" />
      </h1>
    </xsl:if>	
    ITEM<xsl:value-of select="position()"/>
<xsl:value-of select="."/>
  </xsl:for-each>
</xsl:template>

</xsl:stylesheet>

In the above solution, though numbers are getting
generated properly, but to output <h1> tags at the
right place, I had to write a slightly complex syntax
* xsl:if test="name(preceding-sibling::*[1]) = 'h1'" *

I have used the Xalan nodeset extension function.  The
syntax -- xalan:nodeset, can be replaced by
vendor:node-set for a different XSLT processor..

Would also like to have your comments if any to
improve the above XSL.

This _also_ completes my answer..

Regards,
Mukul


--- Wendell Piez <wapiez@xxxxxxxxxxxxxxxx> wrote:
> The two-pass solution would simply be:
> 
> pass 1: sort and create output
> pass 2: number
> 
> The node-set-extension-based solution would be the
> same, except that pass 1 
> would be bound to a variable, then that variable's
> value (a 
> result-tree-fragment) changed to a node-set (in a
> second variable 
> declaration); then you'd apply templates to that
> node set to get the numbering.
> 
> I'd go into more detail but I'm kinda swamped at the
> moment.... :->
> 
> Cheers,
> Wendell
> 
> 
> 
> 
> 
>
======================================================================
> Wendell Piez                           
> mailto:wapiez@xxxxxxxxxxxxxxxx
> Mulberry Technologies, Inc.               
> http://www.mulberrytech.com
> 17 West Jefferson Street                    Direct
> Phone: 301/315-9635
> Suite 207                                         
> Phone: 301/315-9631
> Rockville, MD  20850                                
> Fax: 301/315-8285
>
----------------------------------------------------------------------
>    Mulberry Technologies: A Consultancy Specializing
> in SGML and XML
>
======================================================================
> 
> 
>  XSL-List info and archive: 
> http://www.mulberrytech.com/xsl/xsl-list
> 


__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com

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