From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
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>, Peter Eisentraut <peter_e(at)gmx(dot)net> |
Subject: | Re: Building PDFs error: \pdfendlink ended up in different nesting level than \pd |
Date: | 2011-02-11 22:40:43 |
Message-ID: | 1297463798-sup-9930@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
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(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Thom Brown | 2011-02-12 01:46:09 | Non-existent cs_log function |
Previous Message | Peter Eisentraut | 2011-02-09 21:44:16 | Re: [PATCH] Fix documentation about PL/Python exception handling |