RE: table column

Ah - in almost all places where I have used this, I have gotten away
with it. the only exception was passing the output stream from a sax
transform to the input of a fop process. In that case, passing via a
temporary String did the trick (but I needed to re-parse the XML
afterwards, so there was a cost).

To date I haven't used the native transformer in Mozilla or Netscape,
but have rather had separate xslt processes server-side, so I hadn't
realised this would be a problem for them.

I will go read the FAQ a bit :) That said, my answer did seem to solve
the original poster's problem :)

Given that my answer was incorrect as an approach, though, how would one
go about doing what was described in xsl 1?

<xsl:param name="cellcount" select="3"/>
<!-- how many cells d'you want in a row? -->

<xsl:template match="cell">
  <xsl:if test="(count(preceding-sibling::cell) mod $cellcount) = 1">
    <tr>
      <xsl:for-each select=".|following-sibling::cell[$cellcount - 1]">
        <td>
           <xsl:apply-templates/>
        </td>
      </xsl:for-each>
    </tr>
  </xsl:if>
</xsl:template>

Cheers,
Wendell

___&&__&_&___&_&__&&&__&_&__&__&&____&&_&___&__&_&&_____&__&__&&_____&_&&_
    "Thus I make my own use of the telegraph, without consulting
     the directors, like the sparrows, which I perceive use it
     extensively for a perch." -- Thoreau