See
http://sourceforge.net/tracker/index.php?func=detail&aid=482818&group_id=21935&atid=384107
The vast majority of documentation relies on stylesheets and
processing tools to generate tables of contents, but there are cases
where a manually generated TOC is useful or necessary.
The existing markup for TOCs is probably more complex than it needs to
be (and it would need to be extended to handle all of the flavors of
markup that have been added since it was designed).
This RFE suggests simplifying the model to:
<!ELEMENT ToC - O ((%bookcomponent.title.content;)?,
(%component.mix;)*, (ToCDiv* | ToCEntry*))
%ndxterm.exclusion;>
<!ATTLIST ToC
%pagenum.attrib;
%common.attrib;
%toc.role.attrib;
%local.toc.attrib;
>
<!ELEMENT ToCDiv - O ((%sect.title.content;)?, ((%
tocdivcomponent.mix;)*,
ToCEntry+))>
<!ATTLIST ToCDiv
%linkend.attrib; --to element that this entry
represents--
%pagenum.attrib;
%common.attrib;
%toc.role.attrib;
%local.toc.attrib;
>
<!ELEMENT ToCEntry - - ((%para.char.mix;)+,ToCEntry*)>
<!ATTLIST ToCEntry
%linkend.attrib; --to element that this entry
represents--
%pagenum.attrib;
%common.attrib;
%tocentry.role.attrib;
%local.tocentry.attrib;
>
Have you ever generated a manual TOC? Does that look acceptable?
Be seeing you,
norm
--
Norman Walsh <[EMAIL PROTECTED]> | We are afraid of the old age which
http://www.oasis-open.org/docbook/ | we may never attain.--La Bruy\`ere
Chair, DocBook Technical Committee |
