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 <pgsql-docs-owner+archive@lists.postgresql.org>)
	id 1jNOpF-0006BO-Tm
	for pgsql-docs@arkaria.postgresql.org; Sat, 11 Apr 2020 22:42:09 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-docs-owner+archive@lists.postgresql.org>)
	id 1jNOpD-0002zX-Lt
	for pgsql-docs@arkaria.postgresql.org; Sat, 11 Apr 2020 22:42:07 +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 <tgl@sss.pgh.pa.us>)
	id 1jNOpD-0002zQ-Fn
	for pgsql-docs@lists.postgresql.org; Sat, 11 Apr 2020 22:42:07 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1jNOp5-0003Ly-Ce
	for pgsql-docs@lists.postgresql.org; Sat, 11 Apr 2020 22:42:07 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id 03BMfufJ006163;
	Sat, 11 Apr 2020 18:41:56 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Corey Huinker <corey.huinker@gmail.com>
cc: Alexander Lakhin <exclusion@gmail.com>, pgsql-docs@lists.postgresql.org
Subject: Re: Getting our tables to render better in PDF output
In-reply-to: 
 <CADkLM=dtbn6kyt6Qoqy+mj5YOgcGK+rQ6WpkQm-cggdR2WJceQ@mail.gmail.com>
References: <20200212221818.GA15503@alvherre.pgsql>
 <23574.1581555393@sss.pgh.pa.us> <10810.1581883655@sss.pgh.pa.us>
 <5d1f5b72-1b4a-6e15-6730-d94e2252a073@gmail.com>
 <525a6c9e-a4e2-cd8f-54b6-b69f40d70289@gmail.com>
 <701.1586638307@sss.pgh.pa.us>
 <CADkLM=dtbn6kyt6Qoqy+mj5YOgcGK+rQ6WpkQm-cggdR2WJceQ@mail.gmail.com>
Comments: In-reply-to Corey Huinker <corey.huinker@gmail.com>
	message dated "Sat, 11 Apr 2020 18:14:16 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <6161.1586644916.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Sat, 11 Apr 2020 18:41:56 -0400
Message-ID: <6162.1586644916@sss.pgh.pa.us>
List-Id: <pgsql-docs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-docs@lists.postgresql.org>
List-Owner: <mailto:pgsql-docs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-docs>
Precedence: bulk

Corey Huinker <corey.huinker@gmail.com> writes:
> If it's ok to work on doc patches during the feature freeze, and if we'r=
e
> already tweaking function documentation, would it be possible to add in
> anchor ids to function definitions so that we could reference specific
> functions (or rather the family of functions that share a name like this=
:
> https://www.postgresql.org/docs/devel/functions-datetime.html#FUNCTION-D=
ATE-PART
> or similar. I tried it out just now, and the anchoring works, but there'=
s
> no obvious place to acquire the anchored link, so presumably we'd
> anchor-ize the function name itself.

Don't have a strong opinion about that, but it'd sure be a lot of new
anchors.  Is that going to be a problem for the docs toolchain?  If
the anchors are attached to individual function names rather than
sections or paragraphs, do they actually work well as link references?
(I'm particularly wondering how an <xref> would render.)

			regards, tom lane