pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Corey Huinker <corey.huinker@gmail.com>
Cc: Alexander Lakhin <exclusion@gmail.com>
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: Getting our tables to render better in PDF output
Date: Mon, 13 Apr 2020 12:28:57 -0400
Message-ID: <6694.1586795337@sss.pgh.pa.us> (raw)
In-Reply-To: <CADkLM=caPwA=tqT-E7crtN4RWRMdGL3_N60q-V_s7xFFKahwYA@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>
	<6162.1586644916@sss.pgh.pa.us>
	<CADkLM=dAL86DTUEZY4rigdnB5-zTa0rQvz-fdSUmXqDV3zTQuQ@mail.gmail.com>
	<10438.1586752582@sss.pgh.pa.us>
	<CADkLM=caPwA=tqT-E7crtN4RWRMdGL3_N60q-V_s7xFFKahwYA@mail.gmail.com>

Corey Huinker <corey.huinker@gmail.com> writes:
> I was thinking that there were references that included parameters, but I'm
> not finding any with actual parameter values, so at most we'd lose the "()"
> of a reference.

We could possibly stick the parens into the indexterm text.  Arguably
that's an improvement on its own merits, since it'd become clearer which
index entries are function names.  If you don't want that, another idea is
to put xreflabel options that include the parens into the indexterm tags.
Or we can just standardize on not having parens, but personally I like
them.  Without parens, for clarity you really have to write "function
<function>foo</function>" which is redundant-looking in the XML and hence
easy to get wrong.

> Assuming we want to make the anchors visible, we need a way for people to
> discover the anchors we've made, and my thought there is that we make the
> first definition a non-xref link to the indexterm just above it. Any
> thoughts on what the best way to do that is?

I'm not really buying into that as a requirement.  For one thing, the
anchor name will be 100% predictable.

One thing that I noticed while playing with this last night is that
even though <xref> or <link> links will take you right to the exact
table entry, the index entries generated from the indexterms only
point to the page.  That seems pretty sad, why isn't it better?

			regards, tom lane





view thread (29+ messages)  latest in thread

Message-ID: <6694.1586795337@sss.pgh.pa.us>
Permalink:  ../6694.1586795337@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/6694.1586795337@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, corey.huinker@gmail.com, exclusion@gmail.com, pgsql-docs@lists.postgresql.org
  Subject: Re: Getting our tables to render better in PDF output
  In-Reply-To: <6694.1586795337@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox