Hi Aaron,
Thanks, yes you are probably right.
The "book" used to be an Docbook book, with a proper TOC and everything.
Now, I built a tool to publish a website out of a collection of
articles, so I ended up converting the chapters to articles.
What I was missing was the old kind of TOC. Where the Book had a TOC and
also each chapter had a small TOC.
I concentrated to much on getting <toc> to work in this context as it
"felt right" than to look at other options.
Thanks, I will have another look on what markup could fit better.
/Fred
On 01/24/2013 01:49 PM, Aaron DaMommio wrote:
Your manual toc doesn't sound much like a TOC. Isn't it really just a
set of cross-references or links that you can put in an itemized list or
some other structure. If it doesn't express the contents of its
container, how is it a table of contents?
If that doesn't make sense to you, then show us what your manual TOC
looks like exactly, so we can comment further. I don't understand why
you'd want to use a <toc> element for this manual stuff.
--Aaron
---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
