Re: [xsl] ACCESSING SPECIFIC CDATA FIELD

[<viniciuscamara@xxxxxxxxxxxx>]

David, drkm, Michael and All(fellows, friends, guys [lol] ),
Thanks a lot!

I discovered how many nodes and your positions. Now, I can return to 
Client(Browser) the correct information. And, I forgot to testing 
<xsl:value-of select='text()[2]'/>. So, let me running.

Best Regards,
See Ya!!!!


----- Original Message ----- 
From: "David Carlisle" <davidc@xxxxxxxxx>
To: <xsl-list@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Tuesday, December 13, 2005 2:46 PM
Subject: Re: [xsl] ACCESSING SPECIFIC CDATA FIELD


> >  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
> ________________________________________________________________________


	

	
		
_______________________________________________________ 
Yahoo! doce lar. Faga do Yahoo! sua homepage. 
http://br.yahoo.com/homepageset.html