Обсуждение: pgsql: Tweak wording in sequence-function docs to avoid PDF build failu
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 ------ master Details ------- http://git.postgresql.org/pg/commitdiff/a03ae56e40d7b401ebf93f5732e89ef8cb5237f9 Modified Files -------------- doc/src/sgml/func.sgml | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-)
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
Andrew Dunstan <andrew@dunslane.net> writes:
> On 06/27/2013 12:28 AM, Tom Lane wrote:
>> Tweak wording in sequence-function docs to avoid PDF build failures.
> 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?
It's been discussed repeatedly in pgsql-docs, see latest iteration
yesterday.
regards, tom lane