Hi Tim,
Actually, you could generate the book's TOC from the information in the olink
database. The <div> elements have the same nested structure as the book, and the
title and hrefs are there.
Regarding the chapter numbers, those could be looked up without being passed in
individually. If your stylesheet opens the olink database, it could use xpath to
locate the div whose @element is chapter and whose @targetptr matches the chapter id
attribute that is currently being processed. The templates in common/olink.xsl show
how to open it and access elements from it.
Since the chapter number might be used in several places (figure and table numbers,
section numbers), you should customize the template with match="chapter" and
mode="label.markup" to output the chapter number from the olink database. That mode
is used by all the templates that need the chapter number.
Bob Stayton
Sagehill Enterprises
[email protected]
----- Original Message -----
From: "Tim Arnold" <[email protected]>
To: <[email protected]>
Sent: Wednesday, August 17, 2011 12:57 PM
Subject: [docbook-apps] processing chapters in parallel
Hi,
I have a few large books (~13mb) that I'm processing to html with the
1.76.1 stylesheets. Obviously that takes a while, so I wanted to ask
about what issues will I need to take care of if I process the book
chapter by chapter instead of as one monolithic book.
I have the book.xml, and the separate book_chapter.xml files with an
olinkdb.xml database for the olinks (generated from the book.xml
file).
The two problems I can see so far is that
(1) I won't have a book table of contents and
(2) I'll have to figure out how to pass in each chapter's number to
match the numbers in the generated olinkdb.xml file
These seem like solvable problems. Is there anything I'm missing that
might bite me later on?
thanks for any ideas, information.
--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]
