Re: [DOCS] Building PDFs error: \pdfendlink ended up in different nesting level than \pd
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 The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
[DOCS] Non-existent cs_log function
It's been pointed out that on the pl/pgsql control structures page (http://www.postgresql.org/docs/9.0/interactive/plpgsql-control-structures.html) there's an example using a cs_log function, which doesn't exist. I'm assuming this is supposed to be an example of a custom logging function someone might have, but it might cause less confusion if these were changed to RAISE calls, or something else that exists. What do you think? -- Thom Brown Twitter: @darkixion IRC (freenode): dark_ixion Registered Linux user: #516935 -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
Re: [DOCS] Building PDFs error: \pdfendlink ended up in different nesting level than \pd
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. -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
