Ahh great, thanks for the speedy fix.
An embarassing bug, which happens only when the value of the name attribute
uses curly braces but is nevertheless a compile-time string literal. Having
established that the value is known at compile time, it then goes on to test
that the value as written (that is, "{'b:blah'}") is a valid QName.
A fix is at:
https://sourceforge.net/tracker/index.php?func=detail&aid=1114286&group_id=2
9872&atid=397617
Michael Kay
http://www.saxonica.com/
-----Original Message-----
From: Jack Matheson [mailto:jack(_at_)snazzypost(_dot_)com]
Sent: 01 February 2005 19:05
To: xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com
Subject: [xsl] xsl:element name AVT
I'm getting some unexpected results in the following
stylesheet, and was
wondering if anyone could lend some insight:
<?xml version="1.0"?>
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"; xmlns:a="aa"
xmlns:b="bb">
<xsl:template match="/">
<xsl:element name="{'b:blah'}"/>
</xsl:template>
</xsl:stylesheet>
When the name AVT gets expanded, I expect the prefix 'b' to
be in scope
at this point in the stylesheet.
Saxon 8.2 gives this error:
Error at xsl:element on line 4 of file:elem_avt_ns.xsl:
Element name is not a valid QName
Xalan appears to give the result I expect...is this another case of
"assuming XSLT 1.0 semantics in an XSLT 2.0 environment" ?
--~------------------------------------------------------------------
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>
--~--