RE: Re: xsl-list Digest 28 May 2008 05:10:01 -0000 Iss

> Equally adjacent text nodes are merged, so nested value-of's 
> are pointless:
> 
> <xsl:value-of separator="xx">
>   <xsl:value-of select="/root/node[1]"/>
>   <xsl:value-of select="/root/node[2]"/> </xsl:value-of>
> 
> ...here the output is "foobar" as "foo" and "bar" are merged 
> before the outer value-of gets to them.

No, that's not quite true. If you do this:

<xsl:function name="f" as="xs:string">
    <xsl:value-of select="$g/root/node[1]"/>
    <xsl:value-of select="$g/root/node[2]"/>
</xsl:function>

you will get a type error because the function is returning two text nodes,
and you can't convert two text nodes to a string. Change it to this:

<xsl:function name="f" as="xs:string">
  <xsl:value-of>
    <xsl:value-of select="$g/root/node[1]"/>
    <xsl:value-of select="$g/root/node[2]"/>
  </xsl:value-of>
</xsl:function>

and it works, because you can convert one text node to a string.

Adjacent text nodes are merged only by an operation that merges them, for
example <xsl:element> or <xsl:value-of>.

Michael Kay
http://www.saxonica.com/