| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | Re: pgsql: Tweak wording in sequence-function docs to avoid PDF build failu |
| Date: | 2013-06-27 13:34:34 |
| Message-ID: | 51CC3F6A.9030407@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
On 06/27/2013 12:28 AM, Tom Lane wrote:
> 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.
Is this issue documented somewhere, so that if it crops up again
somewhere else we know how to identify it and how to fix it?
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-06-27 14:00:58 | Re: pgsql: Tweak wording in sequence-function docs to avoid PDF build failu |
| Previous Message | Robert Haas | 2013-06-27 13:00:20 | pgsql: pgbench: Add long options for all existing short options. |