This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: Testing for Parent Nodes of multiple types
- To: <xsl-list at lists dot mulberrytech dot com>
- Subject: RE: [xsl] Testing for Parent Nodes of multiple types
- From: "Ciaran Byrne" <ciaran dot byrne at 3tl dot com>
- Date: Wed, 14 Mar 2001 17:39:34 -0800
- Reply-To: xsl-list at lists dot mulberrytech dot com
The reason why I check the element types of the parent node
is so that I can create the parent node if it isn't the
correct element type.
The purpose of my XSL is to scan some content inserting/ removing
elements in order to achieve conformance with the DTD.
The content I receive is not always well-formed. By passing
it through my XSL I could attempt to achieve well-formedness.
Unless... anyone has any better ideas to do this !!
-----Original Message-----
From: owner-xsl-list@lists.mulberrytech.com
[mailto:owner-xsl-list@lists.mulberrytech.com]On Behalf Of David
Carlisle
Sent: Wednesday, March 14, 2001 8:57 AM
To: xsl-list@lists.mulberrytech.com
Subject: Re: [xsl] Testing for Parent Nodes of multiple types
} <xsl:if test="parent::p or parent::b or parent::i or parent::u or
} parent::td">
} ...
} </xsl:if>
} Is anyone aware of a more efficient way to implement this ?
Not in general, but it depends what you are doing. Rather than
going down to the child and then going back and worrying about what the
parent was, it might be simpler to do whatever is necessary at the level
of the parent (ie in the templates for p and friends). Hard to say
without knowing more context.
David
_____________________________________________________________________
This message has been checked for all known viruses by Star Internet
delivered
through the MessageLabs Virus Control Centre. For further information visit
http://www.star.net.uk/stats.asp
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list