| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | 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-02-12 07:44:10 |
| Message-ID: | 1297496650.6286.1.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2011-02-13 14:52:51 | Re: [GENERAL] Gripe: bytea_output default => data corruption |
| Previous Message | Thom Brown | 2011-02-12 01:46:09 | Non-existent cs_log function |