<xsl:template match="text()"> <!-- in the
text node the
replacement of characters with font tags is done-->
<xsl:choose>
<xsl:when test="not(string(.))" />
<!-- test if
textcontent is empty -->
<xsl:otherwise>
<xsl:call-template name="find_char1" >
Some more stuff ...
</xsl:otherwise> <!-- end textcontent
is not empty
-->
</xsl:choose>
</xsl:template>
Incidentally, when I see a template rule whose body consists entirely of an
xsl:choose, my preference is always to split it into one rule for each
branch of the choose:
<xsl:template match="text()[not(string(.))]"/>
<xsl:template match="text()[string(.)]">
<xsl:call-template name="find_char1" >
Some more stuff ...
</xsl:template>
This would also fix the priorities...
Michael Kay
http://www.saxonica.com/
--~------------------------------------------------------------------
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>
--~--