9.0 PDF build broken

Started by Peter Eisentrautover 11 years ago4 messages
#1Peter Eisentraut
peter_e@gmx.net

Mysteriously, commit 6b2a1445ec8a631060c4cbff3f172bf31d3379b9 has broken
the PDF build (openjade + pdfjadetex) in the 9.0 branch only. The error
is

[256.0.28
! pdfTeX error (ext4): \pdfendlink ended up in different nesting level than \pd
fstartlink.
\AtBegShi@Output ...ipout \box \AtBeginShipoutBox
\fi \fi
l.241723 ...char95{}stat\char95{}file('filename');

! ==> Fatal error occurred, no output PDF file produced!
Transcript written on postgres-A4.log.
make: *** [postgres-A4.pdf] Error 1

I have reproduced this on two different platforms, and it affects only
this branch. I guess this change might have caused the page boundaries
to shift in an unfortunate way. I seem to recall we have had similar
problems before. Does anyone remember?

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: Peter Eisentraut (#1)
Re: 9.0 PDF build broken

Peter Eisentraut <peter_e@gmx.net> writes:

Mysteriously, commit 6b2a1445ec8a631060c4cbff3f172bf31d3379b9 has broken
the PDF build (openjade + pdfjadetex) in the 9.0 branch only. The error
is

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

Oh, not that again.

I have reproduced this on two different platforms, and it affects only
this branch. I guess this change might have caused the page boundaries
to shift in an unfortunate way. I seem to recall we have had similar
problems before. Does anyone remember?

Yeah. This is caused by a hyperlink whose displayed text crosses a page
boundary. The only known fix is to change the text enough so the link
no longer runs across a page boundary. Unfortunately, pdfTeX is pretty
unhelpful about identifying exactly where the problem is. I seem to
recall having posted a recipe about finding such problems.

regards, tom lane

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

#3Tom Lane
tgl@sss.pgh.pa.us
In reply to: Tom Lane (#2)
Re: 9.0 PDF build broken

I wrote:

Yeah. This is caused by a hyperlink whose displayed text crosses a page
boundary. The only known fix is to change the text enough so the link
no longer runs across a page boundary. Unfortunately, pdfTeX is pretty
unhelpful about identifying exactly where the problem is. I seem to
recall having posted a recipe about finding such problems.

Ah, found it:
/messages/by-id/9473.1296172647@sss.pgh.pa.us

regards, tom lane

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

#4Andres Freund
andres@2ndquadrant.com
In reply to: Tom Lane (#2)
Re: 9.0 PDF build broken

On 2014-05-15 22:27:42 -0400, Tom Lane wrote:

Peter Eisentraut <peter_e@gmx.net> writes:

Mysteriously, commit 6b2a1445ec8a631060c4cbff3f172bf31d3379b9 has broken
the PDF build (openjade + pdfjadetex) in the 9.0 branch only. The error
is

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

I have reproduced this on two different platforms, and it affects only
this branch. I guess this change might have caused the page boundaries
to shift in an unfortunate way. I seem to recall we have had similar
problems before. Does anyone remember?

Yeah. This is caused by a hyperlink whose displayed text crosses a page
boundary. The only known fix is to change the text enough so the link
no longer runs across a page boundary. Unfortunately, pdfTeX is pretty
unhelpful about identifying exactly where the problem is. I seem to
recall having posted a recipe about finding such problems.

Hm. Could a nonbreaking space be used inside such links to prevent the
issue (i.e. &nbsp;)? That seems slightly more robust than trying to
rephrase sentences to avoid the issue.
It'd even be nicer if those could be added automagically in the tex
conversio. I have no idea how that works right now though.

Greetings,

Andres Freund

--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers