On Mon, Feb 07, 2005 at 04:01:44PM +0100, Michael Wiedmann <[EMAIL PROTECTED]> wrote: > Mike Hommey <[EMAIL PROTECTED]> wrote: > > > Taken from: > > http://www.w3.org/TR/xslt#named-templates > > > > "It is an error if a stylesheet contains more than one template with the > > same name and same import precedence." > > But see also: > http://www.w3.org/TR/xslt#conflict > > "It is possible for a source node to match more than one template rule. The > template rule to be used is determined as follows:..." > > "It is an error if this leaves more than one matching template rule. An XSLT > processor may signal the error; ..."
That refers to how to *match* a template (i.e. through xsl:apply-templates), not how to resolve a named one (i.e. through xsl:call-template). > I understand that xsltproc/libxslt acts according to this ("may signal..."). > In previous versions xsltproc/libxslt "recovered" from such a situation. It > would be good to know the reason why Daniel changed this. Because it is the expected behaviour. Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]