OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-apps message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [docbook-apps] processing chapters in parallel

Hi Bob, everyone,
Thanks for your guidelines. I will create toc, etc by using the olink
data after processing the chapters in parallel.

As for the chapter numbering issue, I seem to have chapter numbering
working now, using the following code. Please take a look and let me
know if I'm missing something or have done something clunky. Mainly I
fear that this template will cause performance problems since I expect
it is a pretty expensive template to call often, with it opening that
big olinkdb.xml file every time.

First I open the entire database of olinks, which spans several books.
The first variable is the nodeset of olink data for the current book.
The second variable is the id for the current chapter.
The third variable is the element in the olink data that corresponds
to the current chapter.

The template simply returns the value of the number attribute of the element.

<xsl:template match="d:chapter" mode="label.markup" >
  <xsl:variable name="olink_data"
  <xsl:variable name="chapid" select="//d:chapter/@xml:id" />
  <xsl:variable name="chapelem"
  <xsl:value-of select="$chapelem/@number"/>

Thanks for any feedback or optimizations.
--Tim Arnold

On Thu, Aug 25, 2011 at 1:22 PM, Bob Stayton <bobs@sagehill.net> wrote:
> 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
> bobs@sagehill.net
> ----- Original Message ----- From: "Tim Arnold" <jtim.arnold@gmail.com>
> To: <docbook-apps@lists.oasis-open.org>
> 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: docbook-apps-unsubscribe@lists.oasis-open.org
>> For additional commands, e-mail: docbook-apps-help@lists.oasis-open.org

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]