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 1in9lm-0000oF-TZ for pgsql-docs@arkaria.postgresql.org; Thu, 02 Jan 2020 23:20:47 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1in9lk-0007Mn-Ph for pgsql-docs@arkaria.postgresql.org; Thu, 02 Jan 2020 23:20:44 +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 1in7W7-0004Pg-Rs for pgsql-docs@lists.postgresql.org; Thu, 02 Jan 2020 20:56:27 +0000 Received: from mail-lj1-f195.google.com ([209.85.208.195]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1in7W1-0005xD-RD for pgsql-docs@lists.postgresql.org; Thu, 02 Jan 2020 20:56:26 +0000 Received: by mail-lj1-f195.google.com with SMTP id j26so41939164ljc.12 for ; Thu, 02 Jan 2020 12:56:21 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:reply-to :from:date:message-id:subject:to:cc:content-transfer-encoding; bh=lTgkTiRRXzIY257E0BQuE7IPtvMixwRQ8kLqXAlx0jg=; b=L/GehbIEEfUq8plxNayqHVU3md84g8siWhG7rvKwdVO3owDs/dgiPjz5ijQF408zaU 4YSEZTKqxzRH1luPXLakCGywIIoD5cQ8hgPHzH6bFwDhNMm+AQdjHBkPrkNJqRRxNpK4 ayNYkAgipXrlXZudKGxZhOVF8d97COAFtQ6ZJ6U4dtSKqU2I6TzQxfoZSDtweEvoNW/7 n2jgYoN3xEEIGvoXIeV9OxWOShcL5s8oEmf/YV9Ka7rDA9iR1Z1jYD0XvVq8gSczNjrK dBBXzBgGjYk3TcbTB+Fa9T89V/MOO1xprsDLiPmrAcCO9IxxpihXpFIXG7MKC8r7zc1U VBIg== X-Gm-Message-State: APjAAAW6mFL/8pS6kULpq8Kmt2cQ/XbkppjbUwa7qAwuxiU+lWF0sFxY gto37oBK9G/LiVG5ZqyFkRPZrM1w9fgSrPi5epT61kF+8NVDWA== X-Google-Smtp-Source: APXvYqyXNJ0zbJeL0jrjtHLGVlfOlz95FV8oj7vf5DqtFBVaQ7cgHXEX2j5saC4WOClFbwD47FN+A6woU3wsSf9a2nk= X-Received: by 2002:a2e:9118:: with SMTP id m24mr48456673ljg.105.1577998580090; Thu, 02 Jan 2020 12:56:20 -0800 (PST) MIME-Version: 1.0 References: <157795313902.1159.8389366911343891409@wrigleys.postgresql.org> <20200102155632.GA3922@alvherre.pgsql> In-Reply-To: <20200102155632.GA3922@alvherre.pgsql> Reply-To: helix84@centrum.sk From: helix84 Date: Thu, 2 Jan 2020 21:56:00 +0100 Message-ID: Subject: Re: doc: Add anchors in create_table.sgml To: Alvaro Herrera Cc: pgsql-docs@lists.postgresql.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk 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. Thanks in advance and let me take this opportunity to thank you all for this wonderful piece of software. [1] https://www.postgresql-archive.org/Please-provide-stable-target-anchors= -td2167039.html [2] https://bitbucket.org/dvarrazzo/pg-doc-anchors/src/default/ Regards, ~~helix84 On Thu, Jan 2, 2020 at 4:56 PM Alvaro Herrera wr= ote: > > On 2020-Jan-02, PG Doc comments form wrote: > > > The following documentation comment has been logged on the website: > > > > Page: https://www.postgresql.org/docs/12/sql-createtable.html > > Description: > > > > From 73ad66d721a3f87500857cdc6b1f4d810f2875df Mon Sep 17 00:00:00 2001 > > From: =3D?UTF-8?q?Ivan=3D20Mas=3DC3=3DA1r?=3D > > Date: Thu, 2 Jan 2020 09:15:34 +0100 > > Subject: [PATCH] doc: Add anchors in create_table.sgml > > Can you comment a little on the reason for adding these? I'm not > opposed to doing so, but we don't have them in every possible place (we > have in 607 of ~4300 varlistentries by my count), so it needs some > rationale. > > > -- > =C3=81lvaro Herrera https://www.2ndQuadrant.com/ > PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services