Altova Mailing List Archives
>xsl-list Archive Home
>Recent entries
>Thread Prev - [xsl] How to test if a node is a descendant of a specific ancestor
>Thread Next - [xsl] XSLT Programmer's Reference 2nd: What's new?
RE: [xsl] How to test if a node is a descendant of a specific ancestor
To:
Date: 4/26/2001 7:18:00 AM
> Then I have a template rule in an XSL file that looks like > the following: > > <xsl:template match="//string"> > .......Pseudo code: > <test if the current context node is a descendant of head-row> > <p class="head-row">some content</p> > </test> > > <test if the current context node is a descendant of body-row> > <p class="body-row">some content</p> > </test> > ........... > > > How can I test this? > <xsl:if test="ancestor::head-row">... Alternatively, have two separate template rules, and write xsl:template match="head-row//string" or xsl:template match="body-row//string" Michael Kay Software AG P.S. I have just received my copies of XSLT Programmer's Reference 2nd Edition from the printers, so if you have a copy on order, you should be getting it soon. XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Disclaimer
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

