This is the mail archive of the
docbook-apps@lists.oasis-open.org
mailing list .
Re: [docbook-apps] auto gnerate toc
- From: "Bob Stayton" <bobs at sagehill dot net>
- To: "Wim Lemkens" <wim dot lemkens at tiscali dot be>, <docbook-apps at lists dot oasis-open dot org>
- Date: Mon, 28 Jun 2004 15:28:26 -0700
- Subject: Re: [docbook-apps] auto gnerate toc
- References: <200406282312.17135.wim.lemkens@tiscali.be>
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.
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: Monday, June 28, 2004 2:12 PM
Subject: [docbook-apps] auto gnerate toc
> Hello,
>
> I'm trying to create an extension so I can easily make usecases (in
textform).
> I took a part of the ordererdlist code and adjusted it. But I would like
to
> have an autogenerated toc for these usecases.
>
> I browsed through the sections and autotoc code, but I can't find the
correct
> way to do it.
>
> Where should I start looking?
>
> Thanks,
>
> 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/.
>
>
>
To unsubscribe from this list, send a post to docbook-apps-unsubscribe@lists.oasis-open.org, or visit http://www.oasis-open.org/mlmanage/.