[XSL-LIST Mailing List Archive Home]
[By Thread]
[By Date]
Re: [xsl] manipulating text and not losing elements
Subject: Re: [xsl] manipulating text and not losing elements From: David Carlisle <davidc@xxxxxxxxx> Date: Thu, 13 Oct 2005 16:42:37 +0100 |
> Only one > question: shouldn't it be the ancestor axis and not preceding-sibing > or am I misreading the predicates? > ie something like > text()[ancestor::node()[1][ ancestor::node()[1] can be written as parent::* but otherwise, yes, or no, depending. I correctly translated _my_ question into XSLT. me> XSLT has no access to any tags, so first express that in terms of things me> XSLT can see: me> But what happens in the scenario where I want to remove the numbers me> in the text node right after the indent1 and paragraph elements, But I clearly hadn't looked too carefuly at the posted example I translated right after the indent1 and paragraph tags, into right after the indent1 and paragraph elements, But of course the OP means start tag and so the translation should have been first child of the indent1 and paragraph tags, so something like this: <xsl:template match="*[self::indent1 or self::paragraph]/ text()[1][starts-with(translate(.,'123456789','000000000'),'0')]"> David Moral of the story: don't use the T-word when discussing XSLT, it only serves to confuse. ________________________________________________________________________ This e-mail has been scanned for all viruses by Star. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk ________________________________________________________________________
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] manipulating text and not, Jon Gorman | Thread | Re: [xsl] manipulating text and not, Spencer Tickner |
Re: [xsl] manipulating text and not, James A. Robinson | Date | RE: [xsl] Winddings, symbol etc, Mark Williams |
Month |
Keywords