public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: Josh Kupershmidt <[email protected]>
Cc: pgsql-docs <[email protected]>
Subject: Re: Building PDFs error: \pdfendlink ended up in different nesting level than \pd
Date: Fri, 28 Jan 2011 12:11:51 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

I wrote:
Josh Kupershmidt <[email protected]> writes:
>> I looked around line 1390679 of postgres-US.tex-pdf, where I saw this
>> snippet from seg.sgml:
>> (spaces around the range operator are ignored)

The nearest preceding candidate for a split link seems to be the
reference to table F-25 in the opening paragraph of section F.36.2
(attached PNG shows what it looks like when I build HEAD in US page
size).  Since that sentence is rather badly in need of copy-editing
anyway, I'll go see if I can fix it.  However, it's rather disturbing
that in my build the problem seems to be more than half a dozen lines
away from a page boundary.  I could believe a line or two discrepancy
between different toolchains, but this seems like a lot.

> Something we might consider doing to try to make this more stable is to
> see if we can force more page breaks in the PDF output.  That would
> isolate each chapter or section from changes in others.

In my build, the entire contrib manual is potentially interdependent,
because the sub-sections of Appendix F don't start new pages.  This
seems bad.  What is even more curious is that it looks like the function
"man pages" within the dblink section *do* get forced page breaks.
That is inconsistent to say the least.  How much control do we have over
this type of formatting decision?

			regards, tom lane

view thread (26+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: Building PDFs error: \pdfendlink ended up in different nesting level than \pd
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox