[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xsl-list
Subject:    Re: [xsl] Odd Result-Document Behavior
From:       "Eliot Kimber ekimber () contrext ! com" <xsl-list-service () lists ! mulberrytech ! com>
Date:       2015-12-23 19:28:23
Message-ID: 20151223142748.72568 () lists ! mulberrytech ! com
[Download RAW message or body]

Iım pleased that I found a bug, sorry thatıs it there.

Cheers,

E.

----
Eliot Kimber, Owner
Contrext, LLC
http://contrext.com




On 12/23/15, 1:19 PM, "Michael Kay mike@saxonica.com"
<xsl-list-service@lists.mulberrytech.com> wrote:

>> 
>> It seems unlikely that this is a Saxon bug
>
>Guessing probabilities never got anyone anywhere ;-)
>
>The code looks something like this:
>
>if (getFormatExpression() != null) {
>            ...
>            // TODO: reinstate
>
>//            a chunk of commented out code
>
>I'm never sure when something like this happens whether it means that
>no-one uses the feature, or that no-one reports the bug when they find it
>doesn't work. But it certainly means that there aren't any tests for it.
>
>Logged as a bug at https://saxonica.plan.io/issues/2559. Affects both 9.6
>and 9.7.
>
>The old 9.5 implementation will no longer work because of the
>introduction of packages: xsl:output declarations are scoped to a package
>in 3.0, so the code has to search for an xsl:output declaration of the
>right name, but only in the package that contains the xsl:result-document
>instruction.
>
>Michael Kay
>Saxonica
>
>
--~----------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
EasyUnsubscribe: http://lists.mulberrytech.com/unsub/xsl-list/651070
or by email: xsl-list-unsub@lists.mulberrytech.com
--~--
[prev in list] [next in list] [prev in thread] [next in thread]