Re: [xsl] XSLT 3.0 processor accepting non well-formed XML inputs

Subject: Re: [xsl] XSLT 3.0 processor accepting non well-formed XML inputs
From: "Martin Honnen martin.honnen@xxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Date: Mon, 4 Mar 2019 08:14:32 -0000
Am 04.03.2019 um 06:35 schrieb Mukul Gandhi gandhi.mukul@xxxxxxxxx:
> Hi Martin,
> On Sun, Mar 3, 2019 at 4:44 PM Martin Honnen martin.honnen@xxxxxx 
> <mailto:martin.honnen@xxxxxx> <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx 
> <mailto:xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>> wrote:
>     In the W3C test suite for XSLT 3
>     (,
>     if you can get through to it which has been a challenge at least
>     for me today) there is at least one test case (si-iterate-094.xsl)
>     where xsl:iteral/xsl:break is used and where Saxon (tested here
>     with 9.8 EE) outputs a message saying "early exit" (if run with
>     "-t" option) to indicate it abandoned parsing before reading
>     through to the end of the file.
> I ran this test case with, Saxon EE 9.7.x that comes withB oXygen 19.1, 
> and no issues occur.
> I get the output,
> <?xml version="1.0" encoding="UTF-8"?><out><p>foo bar 
> foobar</p><p>foobar baz foo</p></out>
> Saxon's help says following about -t option,
> Value: on|off
> Meaning: Display version and timing information, and names of output files
> It seems to me, the above cited test case has no correlation with 
> Saxon's -t option.
> PS: I've been using Saxon EE 9.9 trial version earlier, that I had to 
> discontinue as the trial expired.

For me the -t option with Saxon EE and streaming is an important option 
as it turns on messages showing whether certain input documents are 
processed using streaming or a tree is built and it also shows the 
"early exit" message in the case the parser abandons parsing.

Current Thread