Re: Getting our tables to render better in PDF output

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
Cc: Alexander Lakhin <exclusion(at)gmail(dot)com>, pgsql-docs(at)lists(dot)postgresql(dot)org
Subject: Re: Getting our tables to render better in PDF output
Date: 2020-04-13 04:36:22
Message-ID: 10438.1586752582@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

Corey Huinker <corey(dot)huinker(at)gmail(dot)com> writes:
> On Sat, Apr 11, 2020 at 6:41 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Don't have a strong opinion about that, but it'd sure be a lot of new
>> anchors.

> So I can't speak to any scalability issues for adding a bunch of refs,

I did a quick check by adding id tags to all 700-or-so <indexterm>s in
func.sgml (don't get excited, it was a perl one-liner that just added
random id strings). The runtime difference for building the HTML docs
seems to be under 1%, and negligible for PDF output. So it looks like
we don't have to worry about scalability of tagging all the functions.

regards, tom lane

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Dave Cramer 2020-04-13 09:54:26 Re: Improve This Sentence?
Previous Message Corey Huinker 2020-04-13 02:42:23 Re: Getting our tables to render better in PDF output