From: Bruce Momjian <bruce@momjian.us>
Message-Id: <201109051650.p85GoOu14781@momjian.us>
Subject: Re: Building PDFs error: \pdfendlink ended up in
	different nesting level than \pd
In-Reply-To: <1297496650.6286.1.camel@vanquo.pezone.net>
To: Peter Eisentraut <peter_e@gmx.net>
Date: Mon, 5 Sep 2011 12:50:24 -0400 (EDT)
CC: Tom Lane <tgl@sss.pgh.pa.us>, Josh Kupershmidt <schmiddy@gmail.com>,
	pgsql-docs <pgsql-docs@postgresql.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"

Peter Eisentraut wrote:
> 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.

Is this a TODO?  Did we ever decide on this?

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +