[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: DOCBOOK: Re: Simplfying the ToC content model
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? Regards, Gerrit Kuilder 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 > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC