Re: [xsl] why not match text()? (fork from "Novice Question - matching entire text children")

Subject: Re: [xsl] why not match text()? (fork from "Novice Question - matching entire text children")
From: Andrew Welch <andrew.j.welch@xxxxxxxxx>
Date: Tue, 21 Dec 2010 09:48:09 +0000
On 20 December 2010 23:17, David Carlisle <davidc@xxxxxxxxx> wrote:
> On 20/12/2010 23:05, Syd Bauman wrote:
>>
>> b) those experts who spoke of the rare need for matching text()
>>    either don't deal with data like mine -- TEI
>
>
> It's not a matter if what experts may do, so much as a question of what
they
> see others doing on this list (and especially) on the xquery list.
> All the uses you gave consisted of doing string manipulations within text
> content, for that text() can be very reasonable (although you still need to
> be careful about comments) but that isn't the common use you see, which is
>
> using
>
> <xsl:value-of select="element-name/text()"/>
>
> rather than
>
> <xsl:value-of select="element-name"/>
>
> especially in a thread with "novice question" in the subject line, it's a
> reasonable asumption that whatever the answer is, it doesn't need text().
>
> Now you don't count as a novice and probably the originator of the original
> thread isn't either, but still, that's what it says in the subject line....


This might be a common problem from people coming from XQuery... in
XSLT we get the string value of the element or attribute, in XQuery
you get the deep-copy, so there is the habit of specifying string()
everywhere (or text() in the past)



--
Andrew Welch
http://andrewjwelch.com

Current Thread