Hi,
You might describe how you are currently processing the 3,000 page doc: which XSLT
processor, which XSL-FO formatter, which versions. You might get some suggestions for
improvements there.
For modular processing, you can set a "label" attribute on each chapter to the chapter
number. That will override the automatic numbering. That manual chapter number will
also be used in figure, table, and example numbers in that chapter.
For page numbers, you would need to modify the template named 'initial.page.number' in
fo/pagesetup.xsl so that it accepts a command line parameter. That parameter could
pass in the starting page for each chapter, which would presumably be the previous
chapter's last page number plus one.
You are right that the olink database will handle cross references. But there is
currently no implementation of page numbers in olinks because of the difficulty of
getting those page numbers from the output. Are you planning to stitch together the
separate chapter PDFs into a single PDF? I've not tried that with hot links between
PDF files, so I don't know if those would still work.
Book-level TOC and index are problems I don't have a solution for. I would instead
concentrate on speeding up the tools to handle the entire document.
Bob Stayton
Sagehill Enterprises
[email protected]
----- Original Message -----
From: "Tim Arnold" <[email protected]>
To: <[email protected]>
Sent: Tuesday, April 06, 2010 11:26 AM
Subject: [docbook-apps] processing modular docbook
Hi,
I have a document that when printed is about 8000 pages. Because of the time it takes
to process, I'd like to be able to process each chapter separately, but the more I
read, the more I doubt the possibility.
My guess is that if I decide to try it, I'll have to set the numbering for
chapters/tables/examples/figures in each chapter and set up a granular olink database
to handle the cross-refs. And create the book-level toc, index, any HTMLHelp files by
some other means.
I haven't yet tried processing this particular document, but a 3,000 page doc takes
about 2 hours on my FreeBSD machine. The processing uses only one of its cpus of
course, and neither memory or diskspace is a limitation--the processing seems to be
cpu-bound only.
Any advice ?
thanks,
--Tim Arnold
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
