[Dev-luatex] keeping in sync with pdftex changes
Hans Hagen
j.hagen at xs4all.nl
Mon Jan 11 15:41:39 CET 2021
On 1/11/2021 12:51 PM, Ulrike Fischer wrote:
> pdftex will in texlive 2021 change in two places
>
> 1. links where \pdfstartlink is in a different boxing level as
> \pdfendlink are no longer a fatal error but gives only a warning:
>
> x\hbox{\pdfstartlink
> attr {/Border[0 0 1]}
> user{
> /Subtype/Link%
> /A<<%
> /Type/Action%
> /S/URI%
> /URI(blkub)%
> >>%
> } Linktext}
> \pdfendlink
>
> \bye
>
> pdfTeX warning: \pdfendlink ended up in different nesting level than
> \pdfstartl
> ink
hm, so bad nesting is not an error ... anyway
./pdf/pdflink.c 75: normal_error("pdf backend","'endlink'
ended up in vlist");
./pdf/pdflink.c 79: normal_error("pdf backend","'endlink'
ended up in different nesting level than 'startlink'");
./pdf/pdfthread.c 111: normal_error("pdf backend",
"'endthread' ended up in hlist");
./pdf/pdfthread.c 113: normal_error("pdf backend",
"'endthread' ended up in different nesting level than 'startthread'");
If we do that then threads also get a warning instead of an error and we
also won't be picky on a mode change. (So four cases where an error
becomes a warning.)
> 2. There are two new primitives \pdfrunninglinkoff &
> \pdfrunninglinkon which allow to interrupt a running link for
> example in the header or footer.
>
> Would it be possible to get this changes into luatex too?
I assume that is just a 'disable' / 'enable' option registered in some
whatsit, i.e. no fancy split into multiple links case and no keeping
track of nested on/off states? (So just some quick and dirty on/off
handling). Again also for threads I guess.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
More information about the dev-luatex
mailing list