Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jWEwC-0005N1-QB for pgsql-docs@arkaria.postgresql.org; Wed, 06 May 2020 07:57:52 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jWEwB-0007Yy-Nj for pgsql-docs@arkaria.postgresql.org; Wed, 06 May 2020 07:57:51 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jWEwB-0007Yr-I2 for pgsql-docs@lists.postgresql.org; Wed, 06 May 2020 07:57:51 +0000 Received: from mout.kundenserver.de ([212.227.126.134]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jWEw9-0001Nr-4o for pgsql-docs@lists.postgresql.org; Wed, 06 May 2020 07:57:51 +0000 Received: from [192.168.178.43] ([77.190.186.232]) by mrelayeu.kundenserver.de (mreue009 [212.227.15.129]) with ESMTPSA (Nemesis) id 1MfpGL-1ivGHh1YL3-00gKMa; Wed, 06 May 2020 09:57:44 +0200 Subject: Re: Documentation - chapter 52, system catalogs To: pgsql-docs@lists.postgresql.org Cc: daelhithe@hotmail.com References: <158860579891.671.9854443057028888145@wrigleys.postgresql.org> <28161.1588716079@sss.pgh.pa.us> From: =?UTF-8?Q?J=c3=bcrgen_Purtz?= Message-ID: Date: Wed, 6 May 2020 09:57:43 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: <28161.1588716079@sss.pgh.pa.us> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Provags-ID: V03:K1:Uh8apBmXkTSTNKJjsjO+/H43VR408R9xZp5jPVGIowtlToW9umU ehghC5+5MfWnlPGXaEzhVvN03cM19zGFvH/mv2x5XHGIYzI8t7muYNspGDSBL9fZjHCIBy6 izP8sx4IsWt4LRkFpu4k3WjW/XyUqKv7bfUsKFOBtKIebWqf8YTw82swm6eeNiajl9uQyew qblIa231W/UGPD2H7gefA== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:g7ZRR4f/0PE=:wrVP5DiO5GWW2dWvSgw5i6 J1TS27rJxA/46UITCUCVH7wxJnFph5pv1vbydaoVaGTkNoygtPobd7CEYPvXmiQN0S1KR2AVo zCEuToVy6M5ObX1LX2ZSYebN9ofQ4IyDuv0bKkOSunwoSxo8f8IlJpa/kGZsPMJWLcQ3SGS1m MMoxktIgo7FGRGSl42vhenA+p2Z8aReS2rbmci9CqGhQ9FNaOWRgYXgzMSVPIRfNQJY2SywNJ 24w5x6lTaYuKdIj3XswGW3zvL0Wvyeax2VZqyqV8Zg0AkPqoufepvctZiLWywCIW4HvKYMJQF BZ3OWP2Nip3+AHCpPNRSrf7/ORCmf22q882GQEdceeBNUT6X/B6UmyiCvTfIVNbXxT3qFJmbf sW1pWh2r6VJpNKouK3OQnGU+1VGF309Qf2DMIPax0fpo4lJtM3w9DVvYrtJLrVMDkozYtRDuS fUcs36/3RNPubEaq1AdQNaDoR7oz5oMzuCWQ6VzlEGYPCEwhG60HbJR4DpuFmMXBkuIDRc+6+ LGHXun4742fdWkvB3xCBj8fBKjallavWUpE2NzEUKARSBziDAnzBZo6mbA4MLiwsIcqhFXHhK B0D5NpT3YjTh5FrR6MlDO1K/j6ZxPQ6vaUDwZ3wI3Oh2XyQJntY3C/5GTQXM4fZL4nqemNvBb KjGj2618/Gm8iULaCOK1/Eng7yZMCEGMNTjWvpGKYKSRUpvxpUvUkoTpbjZQDuXa7Q+RrMP1U NKTaMgBe50OnsvhJIhacb8DsB5pLQw8xNuuVpwM1pXzmLnhgWb9qKNafVSvFD9bzvWdrLSoXO 1vmF8GGETy0xZSr9phEf2Uk0LsHXUefZar+uhr1TcVi0+uKxhTdI3thmAPJMtdIoHSqjVk7 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk 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 , instead of having it in front > of the chapter preface? > > The same issue exists for the sub-sub-tables-of-contents for s, > though it's less bad because few of those have grown enormous lists > of '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