W3C home > Mailing lists > Public > public-qt-comments@w3.org > September 2005

[Bug 2269] Current template rule within xsl:for-each-group/xsl:fallback

From: <bugzilla@wiggum.w3.org>
Date: Tue, 20 Sep 2005 13:50:33 +0000
To: public-qt-comments@w3.org
Cc:
Message-Id: <E1EHiW1-0002nR-LF@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=2269





------- Additional Comments From mike@saxonica.com  2005-09-20 13:50 -------
An XSLT 2.0 processor never executes the xsl:fallback child of an
xsl:analyze-string or xsl:for-each-group instruction (even in backwards
compatibility mode), so the 2.0 spec doesn't need to say what should happen if
it does. It's up to the 1.0 spec to define what an XSLT 1.0 processor does.

I agree that editorially, it might be clearer to remove xsl:matching-substring
and xsl:non-matching-substring from the second row of the table, and put
xsl:analyze-string there instead. But there's no substantive difference.

Michael Kay (personal response)
Received on Tuesday, 20 September 2005 13:51:17 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:08 UTC