I have this source:
...
<colgroup>
<col/>
<col/>
<col/>
</colgroup>
<colgroup>
<col/>
</colgroup>
...
And this template:
<xsl:template match="col">
<fo:table-column>
<xsl:attribute name="column-number">
<xsl:number count="col" from="ancestor::table//*"/>
</xsl:attribute>
...
</fo:table-column>
</xsl:template>
There's a fault here as you can see. The processor doesn't like what I put
in the 'from' attribute. It can only be children, not "cousins", like here.
Why this limitation? I think the above is pretty much straightforward. :-)
If I write like in the example in XSL (no 'from' attribute), I get problems
like this:
<fo:table-column column-number="1" .../>
<fo:table-column column-number="2" .../>
<fo:table-column column-number="3" .../>
<fo:table-column column-number="1" .../>
It starts over when it steps into the new group. What's the solution?
Gustaf
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list