You could use something a prior respondent posted:
Incidentally this could be rewritten
<xsl:template match="document">
...
<xsl:apply-templates select="child::node()[position() > 2]"/>
<xsl:apply-templates select="child::product">
<xsl:sort.../>
</xsl:apply-templates>
</xsl:template>
Michael Kay
Enhancing it with:
<xsl:template match="document/*[not(product)]">
/template
<xsl:template match="product[position()=1]">
/template
<xsl:template match="product[position() > 1]">
/template
etc.
The idea is that one or more "main" templates select nodes ... which are
processed by other specifically-matching templates.
Some of these secondary templates, say, the non-product-matching ones which
need to handle varying preamble, could be put into a separate stylesheet,
and imported into this one via <xsl:import/>.
Archives of this ng also show how to apply templates based on a
dynamically-determined criterion.
That said, in my limited experience the advisability of using a single
stylesheet to transform markedly different content is suspect.
Regards,
--A
_________________________________________________________________
Don?t just search. Find. Check out the new MSN Search!
http://search.msn.click-url.com/go/onm00200636ave/direct/01/
--~------------------------------------------------------------------
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>
--~--