Re: pgsql: Doc: fix some rendering problems in the PDF docs build.

From: Jeff Davis <pgsql(at)j-davis(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Doc: fix some rendering problems in the PDF docs build.
Date: 2023-05-21 19:11:43
Message-ID: 2579c5a67a5302201a506234b6f78d79c6405351.camel@j-davis.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Sun, 2023-05-21 at 15:21 +0000, Tom Lane wrote:
> Doc: fix some rendering problems in the PDF docs build.
>
> Tweak column widths in a couple of tables to avoid "contents
> ... exceed the available area" warnings.  Remove usage of
> some non-Latin-1 characters.

Thank you for taking care of this.

Aside from the formatting issue, I included some non-ascii characters
in the documentation. Are those OK, or should I replace them with &#
sequences, or find some way to not use such characters at all?

I see a few places with such non-ASCII characters, but only a few, so
it's possible those are mistakes.

Regards,
Jeff Davis

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2023-05-21 19:26:06 pgsql: In clause_is_computable_at(), test required_relids for clone cla
Previous Message Andres Freund 2023-05-21 17:14:01 pgsql: Remove over-eager assertion in ExtendBufferedRelTo()