xsl-list-digest-help(_at_)lists(_dot_)mulberrytech(_dot_)com wrote:
Why don't you just nest the loops instead of putting them adjacent to each
other?
Consider this little stysheet (change 'root' to a proper name) :
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform";>
<xsl:output method="text"/>
<xsl:key name="occupant" match="occupant" use="unitid"/>
<xsl:template match="root">
<xsl:for-each select="unit">
<xsl:variable name="unit" select="."/>
<xsl:variable name="occupants" select="key('occupant',id)"/>
<xsl:choose>
<xsl:when test="$occupants">
<xsl:for-each select="$occupants">
<xsl:value-of select="$unit/name"/> | <xsl:value-of
select="name"/>
<xsl:text> </xsl:text>
</xsl:for-each>
</xsl:when>
<xsl:otherwise>
<xsl:value-of select="$unit/name"/> | Vacant
</xsl:otherwise>
</xsl:choose>
</xsl:for-each>
</xsl:template>
</xsl:stylesheet>
I had something like this (without using keys, as I just don't
understand keys well enough other than to copy other people's examples
:) ); the problem is that I was giving a simplified version of my
problem. There are actually 7 or 8 columns per row, and it just seems
that there must be a way that I don't have to have each column defined
in both the when and the otherwise.
--Russell
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--