Content-Type: text/plain; charset=UTF-8
Cc: Josh Kupershmidt <schmiddy@gmail.com>,
	pgsql-docs <pgsql-docs@postgresql.org>, Peter Eisentraut <peter_e@gmx.net>
Subject: Re: Building PDFs error: \pdfendlink ended up in different nesting
	level than \pd
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
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>
Date: Fri, 11 Feb 2011 19:40:43 -0300
Message-Id: <1297463798-sup-9930@alvh.no-ip.org>
User-Agent: Sup/git
Content-Transfer-Encoding: 8bit

Excerpts from Tom Lane's message of vie ene 28 14:11:51 -0300 2011:

> > 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?

I think this is relative, because it seems we can control it if we're
able to hack the stylesheet.dsl file -- which I know I can't quite
follow.  Peter is the person to ask, I think.

-- 
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support