Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id DFE211337BC8 for ; Fri, 28 Jan 2011 11:11:24 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 88260-05 for ; Fri, 28 Jan 2011 15:11:18 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mail.postgresql.org (Postfix) with ESMTP id 873A91337BD4 for ; Fri, 28 Jan 2011 11:11:17 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id p0SFBG3r019099; Fri, 28 Jan 2011 10:11:17 -0500 (EST) To: Josh Kupershmidt cc: pgsql-docs Subject: Re: Building PDFs error: \pdfendlink ended up in different nesting level than \pd In-reply-to: References: <9473.1296172647@sss.pgh.pa.us> Comments: In-reply-to Josh Kupershmidt message dated "Thu, 27 Jan 2011 23:38:13 -0500" Date: Fri, 28 Jan 2011 10:11:16 -0500 Message-ID: <19098.1296227476@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-5 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201101/50 X-Sequence-Number: 6342 Josh Kupershmidt writes: > Thanks for looking into this further. Both the -US and -A4 PDFs are > still failing for me on a recent git checkout including your change to > catalog.sgml. Hmph. HEAD does build both US and A4 sizes for me, using current Fedora 13 docs toolchain. But given what we now know, it could be sensitive to fairly small deltas in the toolchain, since any small change in spacing decisions might create or remove a problem. > I looked around line 1390679 of postgres-US.tex-pdf, where I saw this > snippet from seg.sgml: > (spaces around the range operator are ignored) Well, you're getting a lot further anyway ;-). But it's real curious that you seem to be hitting these more easily than anyone else ever has. I wonder if there's something about your toolchain that makes the issue more probable. 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. regards, tom lane