docbook-apps

Hi! I have a working Gradle build system that transforms DocBook 5.1
(using an assembly) to a few output mediums. I'm using Saxon 6.5.5 and
the DocBook XSLT 1.0 stylesheets (latest version). When a new writer
chose to use Windows, the Gradle build broke when she ran it locally.

Problem #1 is that the Gradle exec task that assembles the DocBook
assembly using Saxon 6.5.5 won't work under Windows. Saxon complains
that there's "no output file name." Gradle has a terrible problem
consuming the "-o myoutputfile.xml" argument. If I present the "-o"
argument separately, Saxon claims that the output file name is
missing. If I present a "-o myoutputfile.xml" argument, Saxon
complains that "-o myoutputfile.xml" isn't a recognized argument. Has
anyone built a Gradle Exec task that runs Saxon 6.5.5 on Windows? It
works just fine on Linux and MacOS.

Question #2 is: Has anyone had trouble using Saxon9HE with the DocBook
XSLT v1.0 stylesheets? The way the arguments for the later version of
Saxon are structured work much better with Gradle.
(-o:myoutputfile.xml.)

I'm considering switching to the DocBook XSLT 2.0 stylesheets to work
around this problem. That avoids mixing Saxon9HE with the DocBook XSLT
1.0 stylesheets. Has anyone had any trouble migrating to XSLT 2.0?

Thanks for your help!

Peter

Worth asking on the docbook-apps list Peter?
I use 2 for other parts, but for my main (quite large) docbook build I use 1.
I use ant.
HTH

On 10 August 2017 at 05:14, Peter Desjardins
<peter.desjardins.us@gmail.com> wrote:
> Hi! I have a working Gradle build system that transforms DocBook 5.1
> (using an assembly) to a few output mediums. I'm using Saxon 6.5.5 and
> the DocBook XSLT 1.0 stylesheets (latest version). When a new writer
> chose to use Windows, the Gradle build broke when she ran it locally.
>
> Problem #1 is that the Gradle exec task that assembles the DocBook
> assembly using Saxon 6.5.5 won't work under Windows. Saxon complains
> that there's "no output file name." Gradle has a terrible problem
> consuming the "-o myoutputfile.xml" argument. If I present the "-o"
> argument separately, Saxon claims that the output file name is
> missing. If I present a "-o myoutputfile.xml" argument, Saxon
> complains that "-o myoutputfile.xml" isn't a recognized argument. Has
> anyone built a Gradle Exec task that runs Saxon 6.5.5 on Windows? It
> works just fine on Linux and MacOS.
>
> Question #2 is: Has anyone had trouble using Saxon9HE with the DocBook
> XSLT v1.0 stylesheets? The way the arguments for the later version of
> Saxon are structured work much better with Gradle.
> (-o:myoutputfile.xml.)
>
> I'm considering switching to the DocBook XSLT 2.0 stylesheets to work
> around this problem. That avoids mixing Saxon9HE with the DocBook XSLT
> 1.0 stylesheets. Has anyone had any trouble migrating to XSLT 2.0?
>
> Thanks for your help!
>
> Peter
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org
>



--
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
http://www.dpawson.co.uk

2017-08-10 8:30 GMT+02:00 Dave Pawson <dave.pawson@gmail.com>:

> Worth asking on the docbook-apps list Peter?
>

This is the docbooks-apps list, isn't it?


> I use 2 for other parts, but for my main (quite large) docbook build I use
> 1.
> I use ant.
> HTH
>

Peter, you could try giving "-o" and "myoutputfile.xml" as separate
arguments. If you would build this with Go-Cd, it would require you to
configure the build task arguments like this:

```
--some-other-arg
-o
myoutputfile.xml
```

and thus treating every line as a separate argument. Writing it like this
would not work:

```
--some-other-arg
-o myoutputfile.xml
```

You could also try wrapping `myoutputfile.xml` in quotes.


>
> On 10 August 2017 at 05:14, Peter Desjardins
> <peter.desjardins.us@gmail.com> wrote:
> > Hi! I have a working Gradle build system that transforms DocBook 5.1
> > (using an assembly) to a few output mediums. I'm using Saxon 6.5.5 and
> > the DocBook XSLT 1.0 stylesheets (latest version). When a new writer
> > chose to use Windows, the Gradle build broke when she ran it locally.
> >
> > Problem #1 is that the Gradle exec task that assembles the DocBook
> > assembly using Saxon 6.5.5 won't work under Windows. Saxon complains
> > that there's "no output file name." Gradle has a terrible problem
> > consuming the "-o myoutputfile.xml" argument. If I present the "-o"
> > argument separately, Saxon claims that the output file name is
> > missing. If I present a "-o myoutputfile.xml" argument, Saxon
> > complains that "-o myoutputfile.xml" isn't a recognized argument. Has
> > anyone built a Gradle Exec task that runs Saxon 6.5.5 on Windows? It
> > works just fine on Linux and MacOS.
> >
> > Question #2 is: Has anyone had trouble using Saxon9HE with the DocBook
> > XSLT v1.0 stylesheets? The way the arguments for the later version of
> > Saxon are structured work much better with Gradle.
> > (-o:myoutputfile.xml.)
> >
> > I'm considering switching to the DocBook XSLT 2.0 stylesheets to work
> > around this problem. That avoids mixing Saxon9HE with the DocBook XSLT
> > 1.0 stylesheets. Has anyone had any trouble migrating to XSLT 2.0?
> >
> > Thanks for your help!
> >
> > Peter
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org
> > For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org
> >
>
>
>
> --
> Dave Pawson
> XSLT XSL-FO FAQ.
> Docbook FAQ.
> http://www.dpawson.co.uk
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org
>
>


--
Dominik Psenner

That’s exactly what I was going to suggest. (ie passing the “-o” and the file-name as separate parameters).
Some time ago when I got Saxon 6.5.5 working from Ant that’s exactly what I had to do.
Saxon 9 takes “-o:file-name”, ie the colon means that it is a single keyword, where Saxon 6 makes it two “-o file-name”.

Regards,
Richard.



Richard Kerry
BNCS Engineer, SI SOL Telco & Media Vertical Practice

T: +44 (0)20 3618 2669
M: +44 (0)7812 325518
Lync: +44 (0) 20 3618 0778
Room G300, Stadium House, Wood Lane, London, W12 7TA
richard.kerry@atos.net<mailto:richard.kerry@atos.net>

[cid:image002.png@01D311C2.D8BE3CB0]


From: Dominik Psenner [mailto:dpsenner@gmail.com]
Sent: Thursday, August 10, 2017 9:13 AM
To: DocBook Apps <docbook-apps@lists.oasis-open.org>
Subject: Re: [docbook-apps] Gradle build cross-platform - trouble with Saxon 6.5.5 params under Windows



2017-08-10 8:30 GMT+02:00 Dave Pawson < /><mailto:dave.pawson@gmail.com>>:
Worth asking on the docbook-apps list Peter?

This is the docbooks-apps list, isn't it?

I use 2 for other parts, but for my main (quite large) docbook build I use 1.
I use ant.
HTH

Peter, you could try giving "-o" and "myoutputfile.xml" as separate arguments. If you would build this with Go-Cd, it would require you to configure the build task arguments like this:

```
--some-other-arg
-o
myoutputfile.xml
```

and thus treating every line as a separate argument. Writing it like this would not work:

```
--some-other-arg
-o myoutputfile.xml
```

You could also try wrapping `myoutputfile.xml` in quotes.


On 10 August 2017 at 05:14, Peter Desjardins
< /><mailto:peter.desjardins.us@gmail.com>> wrote:
> Hi! I have a working Gradle build system that transforms DocBook 5.1
> (using an assembly) to a few output mediums. I'm using Saxon 6.5.5 and
> the DocBook XSLT 1.0 stylesheets (latest version). When a new writer
> chose to use Windows, the Gradle build broke when she ran it locally.
>
> Problem #1 is that the Gradle exec task that assembles the DocBook
> assembly using Saxon 6.5.5 won't work under Windows. Saxon complains
> that there's "no output file name." Gradle has a terrible problem
> consuming the "-o myoutputfile.xml" argument. If I present the "-o"
> argument separately, Saxon claims that the output file name is
> missing. If I present a "-o myoutputfile.xml" argument, Saxon
> complains that "-o myoutputfile.xml" isn't a recognized argument. Has
> anyone built a Gradle Exec task that runs Saxon 6.5.5 on Windows? It
> works just fine on Linux and MacOS.
>
> Question #2 is: Has anyone had trouble using Saxon9HE with the DocBook
> XSLT v1.0 stylesheets? The way the arguments for the later version of
> Saxon are structured work much better with Gradle.
> (-o:myoutputfile.xml.)
>
> I'm considering switching to the DocBook XSLT 2.0 stylesheets to work
> around this problem. That avoids mixing Saxon9HE with the DocBook XSLT
> 1.0 stylesheets. Has anyone had any trouble migrating to XSLT 2.0?
>
> Thanks for your help!
>
> Peter
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org<mailto:docbook-apps-unsubscribe@lists.oasis-open.org>
> For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org<mailto:docbook-apps-help@lists.oasis-open.org>
>


--
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
http://www.dpawson.co.uk

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org<mailto:docbook-apps-unsubscribe@lists.oasis-open.org>
For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org<mailto:docbook-apps-help@lists.oasis-open.org>



--
Dominik Psenner
Atos, Atos Consulting, Worldline and Canopy The Open Cloud Company are trading names used by the Atos group. The following trading entities are registered in England and Wales: Atos IT Services UK Limited (registered number 01245534), Atos Consulting Limited (registered number 04312380), Atos Worldline UK Limited (registered number 08514184) and Canopy The Open Cloud Company Limited (registration number 08011902). The registered office for each is at 4 Triton Square, Regent’s Place, London, NW1 3HG.The VAT No. for each is: GB232327983.

This e-mail and the documents attached are confidential and intended solely for the addressee, and may contain confidential or privileged information. If you receive this e-mail in error, you are not authorised to copy, disclose, use or retain it. Please notify the sender immediately and delete this email from your systems. As emails may be intercepted, amended or lost, they are not secure. Atos therefore can accept no liability for any errors or their content. Although Atos endeavours to maintain a virus-free network, we do not warrant that this transmission is virus-free and can accept no liability for any damages resulting from any virus transmitted. The risks are deemed to be accepted by everyone who communicates with Atos by email.

</mailto:docbook-apps-help@lists.oasis-open.org></mailto:docbook-apps-unsubscribe@lists.oasis-open.org></mailto:docbook-apps-help@lists.oasis-open.org></mailto:docbook-apps-unsubscribe@lists.oasis-open.org></mailto:peter.desjardins.us@gmail.com></mailto:dave.pawson@gmail.com></docbook-apps@lists.oasis-open.org></mailto:richard.kerry@atos.net>

Hi,

On Thu, 10 Aug 2017 06:14:04 +0200, Peter Desjardins
<peter.desjardins.us@gmail.com> wrote:

> Question #2 is: Has anyone had trouble using Saxon9HE with the DocBook
> XSLT v1.0 stylesheets? The way the arguments for the later version of
> Saxon are structured work much better with Gradle.
> (-o:myoutputfile.xml.)

Just my feedback for question 2: As far as I can tell, I've seen no
problem with Saxon9HE and Docbook XSLT 1.0 stylesheets.

Regards,
BG

Thanks!

I ran into trouble when I tried generating webhelp, which uses chunked
output. I think the chunked output requires a Saxon extension. I'm
guessing that the Saxon extensions in extensions/saxon65.jar don't
work with Saxon 9 HE.

Peter

On Fri, Aug 11, 2017 at 1:47 PM, ben.guillon <ben.guillon@gmail.com> wrote:
> Hi,
>
> On Thu, 10 Aug 2017 06:14:04 +0200, Peter Desjardins
> <peter.desjardins.us@gmail.com> wrote:
>
>> Question #2 is: Has anyone had trouble using Saxon9HE with the DocBook
>> XSLT v1.0 stylesheets? The way the arguments for the later version of
>> Saxon are structured work much better with Gradle.
>> (-o:myoutputfile.xml.)
>
>
> Just my feedback for question 2: As far as I can tell, I've seen no problem
> with Saxon9HE and Docbook XSLT 1.0 stylesheets.
>
> Regards,
> BG

Here is the story on using DocBook XSL 1.0 stylesheets with Saxon 9. Any
XSLT 2.0 processor like Saxon 9 has a backwards compatibility mode that
enables it to process XSLT 1.0 stylesheets, and it does a pretty good
job. It works well with fo output, for example.

But the XSLT 1.0 standard did not have a standard document write element
for writing multiple output documents, which is what HTML chunking
needs. Each XSLT 1.0 processor had to implement their own extension
element to do so. Saxon 6 had saxon:output, Xalan had redirect:write,
etc. The DocBook XSL 1.0 stylesheets has a big xsl:choose statement that
figures out which such element is available in the current process and
employs that to write chunks. It is one of the most complex templates
in DocBook XSL.

In XSLT 2.0, there is a standard document write element, the
xsl:result-document element. The chunking stylesheet in XSL 1.0 of
course does not know about XSL 2.0 elements, so it fails to find an
appropriate output element when run with Saxon 9.

There was a good attempt by Jirka Kosek to include that 2.0 element as a
special case in the 1.0 chunking stylesheet. It basically worked, but
not everything worked, so it was never incorporated into the standard
distribution. If you want to try it out, you can find it here:

https://lists.oasis-open.org/archives/docbook-apps/201103/msg00123.html

He includes the code and the caveats.

Bob Stayton
Sagehill Enterprises
bobs@sagehill.net

On 8/11/2017 11:36 AM, Peter Desjardins wrote:
> Thanks!
>
> I ran into trouble when I tried generating webhelp, which uses chunked
> output. I think the chunked output requires a Saxon extension. I'm
> guessing that the Saxon extensions in extensions/saxon65.jar don't
> work with Saxon 9 HE.
>
> Peter
>
> On Fri, Aug 11, 2017 at 1:47 PM, ben.guillon <ben.guillon@gmail.com> wrote:
>> Hi,
>>
>> On Thu, 10 Aug 2017 06:14:04 +0200, Peter Desjardins
>> <peter.desjardins.us@gmail.com> wrote:
>>
>>> Question #2 is: Has anyone had trouble using Saxon9HE with the DocBook
>>> XSLT v1.0 stylesheets? The way the arguments for the later version of
>>> Saxon are structured work much better with Gradle.
>>> (-o:myoutputfile.xml.)
>>
>>
>> Just my feedback for question 2: As far as I can tell, I've seen no problem
>> with Saxon9HE and Docbook XSLT 1.0 stylesheets.
>>
>> Regards,
>> BG
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: docbook-apps-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org
>
>
>