Thanks, Phil, this is great.

It seems so obvious when someone does it who knows how.... It was the
xsl:for-each that was the red herring, instead I should just take the node
set and trim it down one at a time.

Regards,
Wendell

><xsl:template name="getlongest">
>  <xsl:param name="nodeset"/>
>  <xsl:param name="longest" select="0">
>  <xsl:choose>
>    <xsl:when test="$nodeset">
>      <xsl:choose>
>        <xsl:when test="string-length($nodeset[1]) &gt; $longest">
>          <xsl:call-template name="getlongest">
>            <xsl:with-param name="nodeset" select="$nodeset[position()
>&gt; 1]"/>
>            <xsl:with-param name="longest"
>select="string-length($nodeset[1])"/>
>          </xsl:call-template>
>        <xsl:when>
>        <xsl:otherwise>
>          <xsl:call-template name="getlongest">
>            <xsl:with-param name="nodeset" select="$nodeset[position()
>&gt; 1]"/>
>            <xsl:with-param name="longest" select="$longest"/>
>          </xsl:call-template>
>        </xsl:otherwise>
>      </xsl:choose>
>    </xsl:when>
>    <xsl:otherwise>
>      <xsl:value-of select="$longest"/>
>    </xsl:otherwise>
>  </xsl:choose>
></xsl:template>


======================================================================
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