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] auto gnerate toc


Ah, integrating other titles into the main TOC is a bit harder.

Take a look in autotoc.xsl to see how bridgeheads are handled.  Those are
extra titles that are not part of the hierarchy that can be included in the
TOC if the parameter $bridgehead.in.toc is turned on.

Bob Stayton
Sagehill Enterprises
DocBook Consulting
bobs@sagehill.net


----- Original Message ----- 
From: "Wim Lemkens" <wim.lemkens@tiscali.be>
To: <docbook-apps@lists.oasis-open.org>
Sent: Tuesday, June 29, 2004 5:29 AM
Subject: Re: [docbook-apps] auto gnerate toc


> On Tuesday 29 June 2004 00:28, Bob Stayton wrote:
> > The autotoc code for sections is complex because it recursively
processes
> > nested sections.   Your TOC is more like a list of figures.  Take a look
at
> > the match="book" template in division.xsl.  Look for where it calls the
> > 'list.of.titles' template and selects figure elements for its 'nodes'
> > parameter.  Then add some code to 'list.of.titles' to handle your
titles.
> That creates a seperate list of the usecases after the toc. I would like
to
> have it included in the toc as if it were a section.
>
>
> Greetings,
>
> Wim Lemkens
>
> To unsubscribe from this list, send a post to
docbook-apps-unsubscribe@lists.oasis-open.org, or visit
http://www.oasis-open.org/mlmanage/.
>
>
>




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