This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The content model summary of xsl:analyze-string reads, in part: (xsl:matching-substring?, xsl:non-matching-substring?, xsl:fallback*) But the first example in 15.3 uses: <xsl:analyze-string ...> <xsl:non-matching-substring>...</> <xsl:matchign-substring>...</> </> Which is not technically allowed (as the child elements are in the wrong order).
Decided to fix the example to match the current grammar (after discussing whether to change the grammar instead).
Example fixed in draft Y