This is the mail archive of the
docbook@lists.oasis-open.org
mailing list for the DocBook project.
Re: Re: Simplfying the ToC content model
On Tue, Feb 19, 2002 at 08:10:47PM +0100, Gerrit Kuilder wrote:
> Hello Norm,
>
> this will create very complicated (xpath)formatting rules, for that same
> reason I avoid nested <section>'s and use <sect1>, <sect2>, etc
>
> So why not let the user make the choice for nested (simple) toc or the
> way it is now?
I initially had a similar reaction, but then I decided
that if I needed to create TOCs manually, that I would
include a role attribute to identify the toc level
for each entry:
<tocentry role="chapter">...
<tocentry role="sect1">...
That seems like an appropriate use of role, and
would make xpath queries as simple as
using element names.
Of course, that assumes that you are creating the TOC in
the first place and can add the role values.
Bob Stayton 400 Encinal Street
Publications Architect Santa Cruz, CA 95060
Technical Publications voice: (831) 427-7796
Caldera International, Inc. fax: (831) 429-1887
email: bobs@caldera.com
>
> Norman Walsh wrote:
>
> > / Gerrit Kuilder <gerrit@yours-untildeath.demon.nl> was heard to say:
> > | How would one deal with nested toc's (as it is possible now with
> > | tochap toclevel1 etc)?. I do use it to generate a toc, through an xsl
> > | stylesheet, with the levels to create approriate numbering/formatting.
> >
> > Just nest the tocentrys:
> >
> > <toc><title>My Toc</title>
> > <tocentry><citetitle>Chapter One</citetitle>
> > <tocentry><citetitle>Section One</citetitle></tocentry>
> > <tocentry><citetitle>Section Two</citetitle>
> > <tocentry><citetitle>Section Two.One</citetitle></tocentry>
> > </tocentry>
> > </tocentry>
> > </toc>
> >
> > Be seeing you,
> > norm
> >
> >
>
>
--
Bob Stayton 400 Encinal Street
Publications Architect Santa Cruz, CA 95060
Technical Publications voice: (831) 427-7796
Caldera International, Inc. fax: (831) 429-1887
email: bobs@caldera.com