Re: Building PDFs error: \pdfendlink ended up in different nesting level than \pd

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Josh Kupershmidt <schmiddy(at)gmail(dot)com>, pgsql-docs <pgsql-docs(at)postgresql(dot)org>
Subject: Re: Building PDFs error: \pdfendlink ended up in different nesting level than \pd
Date: 2011-09-05 16:50:24
Message-ID: 201109051650.p85GoOu14781@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

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

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Bruce Momjian 2011-09-05 18:21:46 Re: Couple document fixes
Previous Message Bruce Momjian 2011-09-05 15:56:03 Re: 'literal' for numbers