I think it has
to merge all the text in 'etp' before the 'nvgs' element in
one single text node.
Can someone confirm this?
It should do this, but certainly some releases of some xslt engines have
been known to get this wrong. especially if the input is built from a
W3C DOM node, which does allow adjacent text nodes.
Try adding just as a test
<xsl:for-each select="text()">
text: <xsl:value-of select="position()"/> [<xsl:value-of select="."/>]
</xsl:for-each>
Then you find out how many text nodes your system thinks you have, and
what they each contain.
David
________________________________________________________________________
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
________________________________________________________________________
--~------------------------------------------------------------------
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>
--~--