Subject: Re: Building PDFs error: \pdfendlink ended up in different
	nesting level than \pd
From: Peter Eisentraut <peter_e@gmx.net>
To: Bruce Momjian <bruce@momjian.us>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Josh Kupershmidt <schmiddy@gmail.com>,
	pgsql-docs <pgsql-docs@postgresql.org>
In-Reply-To: <201103111341.p2BDfJP12449@momjian.us>
References: <201103111341.p2BDfJP12449@momjian.us>
Content-Type: text/plain; charset="UTF-8"
Date: Sat, 12 Mar 2011 09:31:30 +0200
Message-ID: <1299915090.21000.0.camel@vanquo.pezone.net>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

On fre, 2011-03-11 at 08:41 -0500, Bruce Momjian wrote:
> Peter, any news on this?

I wasn't planning to work on it.

> 
> ---------------------------------------------------------------------------
> 
> 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.
> > 
> > 
> > 
> > -- 
> > Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
> > To make changes to your subscription:
> > http://www.postgresql.org/mailpref/pgsql-docs
> 
> -- 
>   Bruce Momjian  <bruce@momjian.us>        http://momjian.us
>   EnterpriseDB                             http://enterprisedb.com
> 
>   + It's impossible for everything to be true. +
>