The issue is not reproducible even by us..so not sure.
On Thu, Mar 7, 2019, 11:34 AM Michael Kay mike(_at_)saxonica(_dot_)com <
xsl-list-service(_at_)lists(_dot_)mulberrytech(_dot_)com> wrote:
On 7 Mar 2019, at 16:27, Michael Kay mike(_at_)saxonica(_dot_)com <
xsl-list-service(_at_)lists(_dot_)mulberrytech(_dot_)com> wrote:
The effect of having version="1.0" is that the stylesheet runs in
"backwards compatibility mode", meaning that some constructs behave as
described in XSLT 1.0 / XPath 1.0 rather than as defined in 2.0/3.0. For
example, xsl:value-of applied to a sequence of several nodes displays the
first in 1.0 mode, but throws an error in 2.0 / 3.0 mode.
Correction. xsl:value-of in 2.0 displays all the nodes. I was thinking of
the string() function: in 1.0 this displays the first node, while in 2.0 it
throws an error.
My memory of 1.0 is getting rusty - it's almost 20 years old, after all!
Michael Kay
Saxonica
--~----------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
EasyUnsubscribe: http://lists.mulberrytech.com/unsub/xsl-list/1167547
or by email: xsl-list-unsub(_at_)lists(_dot_)mulberrytech(_dot_)com
--~--