Hi Stefan,
Actually there is a <toc> element defined in DocBook 4 and 5. It can be populated
with manually-written elements, or it can be empty with the expectation that the
stylesheet will generate its content. The XSL stylesheets mostly support it, with a
couple of params to control it:
http://docbook.sourceforge.net/release/xsl/current/doc/html/process.source.toc.html
http://docbook.sourceforge.net/release/xsl/current/doc/html/process.empty.source.toc.html
The default behavior is to generate a TOC local to the current element containing the
toc element. Making it more global would require customization.
*But*, I just noticed that DocBook 5 does not allow a <toc> element at the beginning
of a section element, only at the end. It does allow it at the beginning in DocBook
4, and it does in DocBook5 for chapter, appendix, preface, and topic (new to 5.1). I
think this is a bug in DocBook 5, since putting a toc at the end of a section is
rather odd. I've filed an RFE with the DocBook Technical Committee to get this looked
at.
Bob Stayton
Sagehill Enterprises
[email protected]
----- Original Message -----
From: "Stefan Seefeld" <[email protected]>
To: <[email protected]>; "docbook"
<[email protected]>
Sent: Friday, June 01, 2012 6:34 AM
Subject: [docbook] Re: [docbook-apps] toc customization question
On 06/01/2012 09:18 AM, Tim Arnold wrote:
Hi Dick,
Thanks, I have been reading that section, but it's not that I want to
control the toc on every section, just one section that has a
particular attribute. My question wasn't clear that I do want section
tocs, just not for this particular section.
Allow me to jump in with a somewhat related request:
I have run into other situations where I'd like to be able to control
ToC generation explicitly. For example: In DocBook Slides, I'd like to
generate a ToC for each foilgroup (and highlight the current position).
So far I have done this by customizing the appropriate xsl templates.
However, I think it would be very convenient for authors to be able to
explicitly request a toc at a given place, for example using a "<toc>"
element, akin to "<index>". (This could be further tuned by adding
attributes to indicate whether this should be a toc for the local
subtree, or a global one.)
Does this sound reasonable ? I will cross-post this to the docbook list,
too, as it is essentially a request for the DB grammar itself.
Thanks,
Stefan
--
...ich hab' noch einen Koffer in Berlin...
---------------------------------------------------------------------
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]
