Note that I didn+IBk-t actually doubt the soundness of the spec+IBQ-the XSLT 2
spec is one of few standards whose soundness I accept as a given :-) I
would have considered for-each-as-string-contatenation sound enough and
was pleased to learn that it was better than that.
Cheers,
E.
--
Eliot Kimber
Senior Solutions Architect
"Bringing Strategy, Content, and Technology Together"
Main: 512.554.9368
www.reallysi.com
www.rsuitecms.com
On 1/10/14, 4:03 PM, "Imsieke, Gerrit, le-tex" <gerrit.imsieke@le-tex.de>
wrote:
This is too rare a moment on any Internet forum: someone tries
something, *reads the spec*, doubts its soundness, asks questions, *gets
qualified answers*, *reads the spec again* +IBM- and ends up *enlightened*.
Then *shares his enlightenment process* with the forum.
Thanks Eliot for sharing, thanks everybody for answering not only this
question, and thanks Tommie et al. @ Mulberry Tech for xsl-list.
Gerrit
On 10.01.2014 21:55, Eliot Kimber wrote:
I think too I was still laboring under the XSLT 1 definition of
<xsl:value-of/>. Taking the time to re-read the definition of value-of
in
XSLT 2 I see that it explicitly generates text nodes. I don+IBk-t think I
ever
realized that before.
This changes everything (at least in the way I approach constructing
result text).
Cheers,
Eliot
--+AH4-------------------------------------------------------------------
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@lists.mulberrytech.com>
--+AH4---
--+AH4-------------------------------------------------------------------
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>
--+AH4---