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 1pJEbB-0006Rk-Cg for pgsql-hackers@arkaria.postgresql.org; Sat, 21 Jan 2023 14:12:01 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pJEb8-0006c1-9U for pgsql-hackers@arkaria.postgresql.org; Sat, 21 Jan 2023 14:11:58 +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 1pJEb8-0006bX-08 for pgsql-hackers@lists.postgresql.org; Sat, 21 Jan 2023 14:11:58 +0000 Received: from janus.karlpinc.com ([173.161.46.12] helo=smtp.karlpinc.com) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pJEb0-00018J-J8 for pgsql-hackers@lists.postgresql.org; Sat, 21 Jan 2023 14:11:56 +0000 Received: from slate.karlpinc.com (unknown [192.168.1.14]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by smtp.karlpinc.com (Postfix) with ESMTPS id DC230A1BD; Sat, 21 Jan 2023 08:11:46 -0600 (CST) Received: from slate.karlpinc.com (localhost [IPv6:::1]) by slate.karlpinc.com (Postfix) with ESMTPS id 9C3413FCE9; Sat, 21 Jan 2023 08:11:46 -0600 (CST) Date: Sat, 21 Jan 2023 08:11:43 -0600 From: "Karl O. Pinc" To: Alvaro Herrera Cc: PostgreSQL Hackers Subject: Re: Doc: Rework contrib appendix -- informative titles, tweaked sentences Message-ID: <20230121081143.322bcf9f@slate.karlpinc.com> In-Reply-To: <20230120142225.3d3be8a3@slate.karlpinc.com> References: <20230120191203.7nyqjbw3qe7xx4ru@alvherre.pgsql> <20230120191238.ds5l4ehuxve4zn42@alvherre.pgsql> <20230120142225.3d3be8a3@slate.karlpinc.com> X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="MP_/OHkLyRrNDkv9+o/u+ATJMvq" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --MP_/OHkLyRrNDkv9+o/u+ATJMvq Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline Attached are 2 v9 patch versions. I don't think I like them. I think the v8 versions are better. But I thought it wouldn't hurt to show them to you. On Fri, 20 Jan 2023 14:22:25 -0600 "Karl O. Pinc" wrote: > Attached are 2 alternatives: > (They touch separate files so the ordering is meaningless.) > > > v8-0001-List-trusted-and-obsolete-extensions.patch > > Instead of putting [trusted] and [obsolete] in the titles > of the modules, like v7 does, add a list of them into the text. v9 puts the list in vertical format, 5 columns. But the column spacing in HTML is ugly, and I don't see a parameter to set to change it. I suppose we could do more work on the stylesheets, but this seems excessive. It looks good in PDF, but the page break in the middle of the paragraph is ugly. (US-Letter) Again (without forcing a hard page break by frobbing the stylesheet and adding a processing instruction), I don't see a a good way to fix the page break. (sagehill.net says that soft page breaks don't work. I didn't try it.) > v8-0002-Page-break-before-sect1-in-contrib-appendix-when-pdf.patch > > This frobs the PDF style sheet so that when sect1 is used > in the appendix for the contrib directory, there is a page > break before every sect1. This puts each module/extension > onto a separate page, but only for the contrib appendix. > > Aside from hardcoding the "contrib" id, which I suppose isn't > too bad since it's publicly exposed as a HTML anchor (or URL > component?) and unlikely to change, this also means that the > contrib documentation can't use
instead of . v9 supports using
instead of just . But I don't know that it's worth it -- the appendix is committed to sect* entities. Once you start with sect* the stylesheet does not allow "section" use to be interspersed. All the sect*s would have to be changed to "section" throughout the appendix and I don't see that happening. Regards, Karl Free Software: "You don't pay back, you pay forward." -- Robert A. Heinlein --MP_/OHkLyRrNDkv9+o/u+ATJMvq Content-Type: text/x-patch Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=v9-0002-Page-break-before-sect1-in-contrib-appendix-when-pdf.patch diff --git a/doc/src/sgml/stylesheet-fo.xsl b/doc/src/sgml/stylesheet-fo.xsl index 0c4dff92c4..9ce36c7279 100644 --- a/doc/src/sgml/stylesheet-fo.xsl +++ b/doc/src/sgml/stylesheet-fo.xsl @@ -132,4 +132,12 @@ + + + + + + + --MP_/OHkLyRrNDkv9+o/u+ATJMvq Content-Type: text/x-patch Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=v9-0001-List-trusted-and-obsolete-extensions.patch diff --git a/doc/src/sgml/contrib.sgml b/doc/src/sgml/contrib.sgml index 12c79b798b..077184d90d 100644 --- a/doc/src/sgml/contrib.sgml +++ b/doc/src/sgml/contrib.sgml @@ -84,6 +84,31 @@ CREATE EXTENSION extension_name; provide access to outside-the-database functionality. + These are the trusted extensions: + + + + + + + + + + + + + + + + + + + + + + + + Many extensions allow you to install their objects in a schema of your choice. To do that, add SCHEMA @@ -100,6 +125,15 @@ CREATE EXTENSION extension_name; component for details. + + These modules and extensions are obsolete: + + + + + + + &adminpack; &amcheck; &auth-delay; --MP_/OHkLyRrNDkv9+o/u+ATJMvq--