public inbox for [email protected]  

help / color / mirror / Atom feed

From: Bruce Momjian <[email protected]>
To: Peter Eisentraut <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: Josh Kupershmidt <[email protected]>
Cc: pgsql-docs <[email protected]>
Subject: Re: Building PDFs error: \pdfendlink ended up in different nesting level than \pd
Date: Mon, 5 Sep 2011 12:50:24 -0400 (EDT)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

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  <[email protected]>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

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

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], [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