public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: Josh Kupershmidt <[email protected]>
Cc: pgsql-docs <[email protected]>
Subject: Re: Building PDFs error: \pdfendlink ended up in different nesting level than \pd
Date: Fri, 28 Jan 2011 10:11:16 -0500
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>

Josh Kupershmidt <[email protected]> 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

view thread (26+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: Building PDFs error: \pdfendlink ended up in different nesting level than \pd
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox