On 06.05.20 00:01, Tom Lane wrote:
> I don't deny that we have a problem here: in the website rendering,
> that text tends to be pushed down out of sight by the chapter's
> sub-table-of-contents. But that issue exists for every chapter
> that's got more than a couple of sections. We shouldn't hack
> around it for just these two chapters. Chapter 9 and Appendix F
> are additional examples where this is a fairly urgent issue.
Generic solutions are always better than individual ones.
> I wonder if we should just drop the sub-table-of-contents material.
> (I'm assuming DocBook can be coerced to do that; but since the PDF
> output has no such material, it seems like it ought to be possible.)
If we drop TOCs, we loose the automatically created links. As a
substitute we would need tables like in example 51.1. So it's again an
individual solution.
> Or ... is there a way to postpone it to the bottom of the page,
> ie just before the first <sect1>, instead of having it in front
> of the chapter preface?
>
> The same issue exists for the sub-sub-tables-of-contents for <sect1>s,
> though it's less bad because few of those have grown enormous lists
> of <sect2>'s.
Swapping TOC and content may work in such cases, but for me it seems to
be a hard work with xslt.
A real generic solution would be an adaption of the HTML output to the
PDF output: two columns with a collapsible menu containing all TOC
information in the left one ('outline' in PDF) and nothing than content
in the right one. But this is a huge change of the look-and-feel as well
as for all technical stuff: HTML, CSS, bootstrap, Javascript, Ajax(?), ... .
--
Jürgen Purtz
