Thanks Tony, I'll keep this makefile tip in mind. But it turns out that
the FO file was deleted by a shell script that was called by the makefile.
Regards,
Mark
On 3/3/2021 11:55 PM, Tony Graham wrote:
On 04/03/2021 04:33, Mark Giffin wrote:
It's starting to come back to me. I think
It's starting to come back to me. I think that the default when creating
a PDF with DocBook XSL is for the FO file to remain there on the drive
unmolested. So I think I need to point a finger at my makefiles. Sorry
to be a bother.
Mark
On 3/3/2021 3:14 PM, Mark Giffin wrote:
I'm using
I'm using DocBook XSL and I'm trying to save the XSL-FO file from PDF
output. Is there a parameter for this?
Thanks,
Mark
-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail:
That worked, thanks a lot Bob. Now I have to set up xerces for my xincludes.
Mark
On 7/12/2020 11:36 PM, Bob Stayton wrote:
The short answer is: The DocBook XSL stylesheets are written in XSL 1,
and work best with Saxon 6.5.5.
Bob Stayton
b...@sagehill.net
On 7/12/2020 11:24 PM, Mark
I'm messing with olinks and I'm trying to generate my target.db files
from the command line (Windows 10) with Saxon HE10-1J and I keep getting
no target.db file and this error:
Writing target.db for book(MailUserGuide)
Can't make chunks with Saxonica's processor.
Error at char 16 in expression
020, at 2:12 AM, Mark Giffin <mailto:m1...@earthlink.net>> wrote:
I have a large collection of user guides in Docbook 4.3 and 5.1, and
they have a top-level Docbook files with a element, and
sub-chapters are pulled in using xincludes like this:
http://www.w3.org/2001/XInclude;&g
I have a large collection of user guides in Docbook 4.3 and 5.1, and
they have a top-level Docbook files with a element, and
sub-chapters are pulled in using xincludes like this:
http://www.w3.org/2001/XInclude;>
my title
etc.
In the interests of