Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1isax5-0004QE-8n for pgsql-docs@arkaria.postgresql.org; Fri, 17 Jan 2020 23:22:55 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1isax3-0004sz-Eq for pgsql-docs@arkaria.postgresql.org; Fri, 17 Jan 2020 23:22:53 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1isax3-0004ox-3v for pgsql-docs@lists.postgresql.org; Fri, 17 Jan 2020 23:22:53 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1isax0-0004vI-LV for pgsql-docs@lists.postgresql.org; Fri, 17 Jan 2020 23:22:51 +0000 Received: from bruce by momjian.us with local (Exim 4.92) (envelope-from ) id 1isaww-0005XU-SQ; Fri, 17 Jan 2020 18:22:46 -0500 Date: Fri, 17 Jan 2020 18:22:46 -0500 From: Bruce Momjian To: Alvaro Herrera Cc: helix84 , pgsql-docs@lists.postgresql.org Subject: Re: doc: Add anchors in create_table.sgml Message-ID: <20200117232246.GD14054@momjian.us> References: <20200103133520.GA29959@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200103133520.GA29959@alvherre.pgsql> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Fri, Jan 3, 2020 at 10:35:20AM -0300, Alvaro Herrera wrote: > Hi, > > On 2020-Jan-02, helix84 wrote: > > > Hi, I prefer to bookmark docs pointing to the exact term I need and > > with pg docs it's often been the case that the exact term doesn't have > > an anchor or only has unstable, generated anchors. So I would very > > much like to add stable anchors in many more places. I haven't > > contributed to pg before, so this patch is me testing the waters. If > > there is interest, I'd like to add stable anchors to wherever we'll > > agree it makes sense - preferably in an automated or semi-automated > > way. > > > > I read an older thread on this topic [1] which links to a custom SGML > > parser in Python for this specific task [2]. I have experience with > > XSLT, but not so much with SGML processing, so I would appreciate if > > you could point me whether a custom parser is the way to go for this > > task or I should look into a more generic SGML processing tool. > > Ah, > https://www.postgresql.org/message-id/AANLkTikAgIyYfwy_2Zj8GafoC7ZFlGv5iCdab1l7VuDp@mail.gmail.com > (We prefer our own archive to GMane's.) That thread is so old that > Peter feels the need to point out that the Git mirror was out of date > with CVS ... I can no longer even remember the commit process for CVS > anymore. We also converted from SGML to XML in the meantime, so you can > probably make do with a standard XML parser without having to write a > custom SGML one. (Daniele Varrazzo's patch ended up as 477319829c2e.) > > TBH I've felt the need for anchors for tags in the > past also (IIRC the runtime-config page would be improved by them), > but I'm not sure about adding them to every single keyword of every > single reference page. Is that really useful? It would be helpful if the release notes could point to specific tables in the docs, rather than just sections. -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription +