Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Un7qR-0000Cq-NZ for pgsql-docs@arkaria.postgresql.org; Thu, 13 Jun 2013 13:45:43 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1Un7qQ-00054b-On for pgsql-docs@arkaria.postgresql.org; Thu, 13 Jun 2013 13:45:42 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Un7qP-00054V-Vl for pgsql-docs@postgresql.org; Thu, 13 Jun 2013 13:45:42 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Un7qM-0000To-0i for pgsql-docs@postgresql.org; Thu, 13 Jun 2013 13:45:41 +0000 Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.5/8.14.5) with ESMTP id r5DDjbMb020927; Thu, 13 Jun 2013 09:45:37 -0400 (EDT) From: Tom Lane To: "Erik Rijkers" cc: pgsql-docs@postgresql.org Subject: Re: pdf does not build anymore In-reply-to: <3b4139a6e0ceea903dd359b7035d5d4a.squirrel@webmail.xs4all.nl> References: <3b4139a6e0ceea903dd359b7035d5d4a.squirrel@webmail.xs4all.nl> Comments: In-reply-to "Erik Rijkers" message dated "Thu, 13 Jun 2013 14:56:54 +0200" Date: Thu, 13 Jun 2013 09:45:36 -0400 Message-ID: <20926.1371131136@sss.pgh.pa.us> X-Pg-Spam-Score: -2.3 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org "Erik Rijkers" writes: > ! pdfTeX error (ext4): \pdfendlink ended up in different nesting level than \pd > fstartlink. Known failure mode. That happens whenever the text of a phrase crosses a page boundary :-(. We've generally worked around it by tweaking the text so that doesn't happen, but of course we're at risk again the next time anyone adds/changes text in the vicinity. Can you identify what linked phrase is causing the problem? Also, FYI, this is claimed to be fixed in TeX Live 2012: https://bugzilla.redhat.com/show_bug.cgi?id=619481 so a toolchain upgrade is the long-term answer. regards, tom lane -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs