pgsql: Tweak wording in sequence-function docs to avoid PDF build failu

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Tweak wording in sequence-function docs to avoid PDF build failu
Date: 2013-06-27 04:28:30
Message-ID: E1Us3os-0002ua-Nn@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Tweak wording in sequence-function docs to avoid PDF build failures.

Adjust the wording in the first para of "Sequence Manipulation Functions"
so that neither of the link phrases in it break across line boundaries,
in either A4- or US-page-size PDF output. This fixes a reported build
failure for the 9.3beta2 A4 PDF docs, and future-proofs this particular
para against causing similar problems in future. (Perhaps somebody will
fix this issue in the SGML/TeX documentation tool chain someday, but I'm
not holding my breath.)

Back-patch to all supported branches, since the same problem could rise up
to bite us in future updates if anyone changes anything earlier than this
in func.sgml.

Branch
------
REL9_2_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/60d7edb835c11f15c1d88f8985795ec4abc480f4

Modified Files
--------------
doc/src/sgml/func.sgml | 9 ++++-----
1 file changed, 4 insertions(+), 5 deletions(-)

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Erik Rijkers 2013-06-27 05:10:29 Re: pgsql: Tweak wording in sequence-function docs to avoid PDF build failu
Previous Message Noah Misch 2013-06-27 00:35:12 pgsql: Refactor aset.c and mcxt.c in preparation for Valgrind cooperati