Обсуждение: pgsql: Doc: fix some rendering problems in the PDF docs build.
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. Discussion: https://postgr.es/m/614600.1684537037@sss.pgh.pa.us Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/b62381d9a23b4b96259cf560e411137656201704 Modified Files -------------- doc/src/sgml/charset.sgml | 21 +++++++++++++++++---- doc/src/sgml/release-16.sgml | 2 +- 2 files changed, 18 insertions(+), 5 deletions(-)
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
Jeff Davis <pgsql@j-davis.com> writes:
> 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.
The PDF toolchain can cope with ISO-8859-1 (Latin-1) characters,
so it's not problematic to use those. I'm not seeing any complaints
from the current build.
regards, tom lane