Subject: Re: Building PDFs error: \pdfendlink ended up in different
	nesting level than \pd
From: Peter Eisentraut <peter_e@gmx.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Josh Kupershmidt <schmiddy@gmail.com>, pgsql-docs
	<pgsql-docs@postgresql.org>
In-Reply-To: <21027.1296234711@sss.pgh.pa.us>
References: <AANLkTim7y4cUFxoMcmC-o_SLAiM7va=3DLtQxa2znh_Q@mail.gmail.com>
	<9473.1296172647@sss.pgh.pa.us>
	<AANLkTikTWpE2UdJzLyvF6ktVRyyftMd_5hZBoUoYA79s@mail.gmail.com>
	<19098.1296227476@sss.pgh.pa.us>  <21027.1296234711@sss.pgh.pa.us>
Content-Type: text/plain; charset="UTF-8"
Date: Sat, 12 Feb 2011 09:44:10 +0200
Message-ID: <1297496650.6286.1.camel@vanquo.pezone.net>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On fre, 2011-01-28 at 12:11 -0500, Tom Lane wrote:
> 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?

There is a parameter that controls whether a references page starts on a
new page.  But that's it.  It's not impossible to hack the stylesheet to
add more page breaks, but that would affect the whole book, not just one
particular chapter.

With the promotion of the contrib stuff, perhaps they should each get
their own chapter in a new part.