DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to
	:cc:content-type:content-transfer-encoding;
	b=f0EOkLTWPpm3Cyn8jbXceiMIV6WpcpmfQwa2uQ9nhrcS8KUEnyIeT/8ip6xjArLmKa
	bhhgKBLlAyLoayKOToIbxbrsozXTvvmaUtQQItbxMf3yQ0R+mnG8AitcMuMHCic0Gna/
	VijzK52aCGcGHVC2O1TRyL4/+96YWRCbcWgAY=
MIME-Version: 1.0
In-Reply-To: <9473.1296172647@sss.pgh.pa.us>
References: <AANLkTim7y4cUFxoMcmC-o_SLAiM7va=3DLtQxa2znh_Q@mail.gmail.com>
	<9473.1296172647@sss.pgh.pa.us>
From: Josh Kupershmidt <schmiddy@gmail.com>
Date: Thu, 27 Jan 2011 23:38:13 -0500
Message-ID: <AANLkTikTWpE2UdJzLyvF6ktVRyyftMd_5hZBoUoYA79s@mail.gmail.com>
Subject: Re: Building PDFs error: \pdfendlink ended up in different
	nesting level than \pd
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-docs <pgsql-docs@postgresql.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Thu, Jan 27, 2011 at 6:57 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Josh Kupershmidt <schmiddy@gmail.com> writes:
>> How did you figure out that the problem was coming from that spot in
>> installation.sgml? I'd be interested to see whether another hack would
>> work in lieu of an actual fix in pdftex.
>
> If you look at the mentioned line number in the tex-pdf file, you can
> figure out where you are in the document, assuming your eyes don't glaze
> over from the incredibly verbose TeX macros first.
>
> (Note: if you just do "make postgres-A4.pdf", make will unhelpfully
> throw away the tex-pdf intermediate file upon error. =A0What I have done
> when I needed to look is to explicitly "make postgres-A4.tex-pdf" and
> then "make postgres-A4.pdf", which keeps make from discarding the
> tex-pdf file when the second step fails. =A0I wonder though if we could
> tweak the makefile to make this less inconvenient.)

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.

I tried the two-step make process you suggested. The second step of
building postgres-US.pdf failed like so:

Overfull \hbox (1.19998pt too wide) in alignment at lines 1390237--1390679
 [] []

Package longtable Warning: Column widths have changed
(longtable)                in table 287 on input line 1390679.

[3987.0.6
! pdfTeX error (ext4): \pdfendlink ended up in different nesting level than=
 \pd
fstartlink.


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)

so I'm guessing some link around that spot is to blame. Perhaps trying
to hack up all these problem spots in the SGML source is a lost cause,
at least for my build environment. I might try pestering folks on the
pdftex mailing list next.

Josh