public inbox for [email protected]  

help / color / mirror / Atom feed

From: Robert Haas <[email protected]>
To: Bruce Momjian <[email protected]>
Cc: 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: Thu, 15 Sep 2011 06:46:29 -0500
Message-ID: <CA+TgmoYmXZCUHKBGO2dntn2pvR9NgiRuLQapCq1JxW77PiuJqA@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>

On Mon, Sep 5, 2011 at 11:50 AM, Bruce Momjian <[email protected]> wrote:
> 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?

Well, some of the contrib modules are such little stupid things that
giving them their own chapter seems excessive.  sepgsql might merit
its own chapter, but dummy_seclabel surely doesn't.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

view thread (26+ messages)

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], [email protected]
  Subject: Re: Building PDFs error: \pdfendlink ended up in different nesting level than \pd
  In-Reply-To: <CA+TgmoYmXZCUHKBGO2dntn2pvR9NgiRuLQapCq1JxW77PiuJqA@mail.gmail.com>

* 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