[pdftex] \pdfendlink ended up in different nesting level than \pdfstartlink

[Ross Moore]

Hi Karl, Alex’s.

It is interesting that you get it as a fatal error. I only get a warning, and there is nothing broken in the PDF.

My pdfTeX is from TeXLive 2021.

I have suspicions about which is the faulty link, but could not confirm these, due to the input encoding. Editing in the file: Left.Eugene.Russian.tex   corrupted the file’s encoding. I’ll need to extract it afresh from the archive.

Primary suspect is the hyperlink in the footnote near the beginning of that chapter.

Other possibilities are ones that occur just on a page-break, or column-break. 

Best of luck in chasing this one.

Hope this helps.

Ross

Sent from my iPhone

> On 25 Oct 2022, at 8:17 am, Karl Berry <karl at freefriends.org> wrote:
> 
> Hi Aleks - thanks for the report.
> 
>    \pdfendlink ended up in different nesting level than \pdfstartlink
> 
> I get the same fatal error with your source file, on the second run, on
> page 276. (After making the many fonts needed.)
> 
> Unfortunately this is not something that can be fixed at the pdftex
> level. pdftex is just reporting what it's seeing in terms of low-level
> PDF output. It is the LaTeX macros that need to avoid the issue. And as
> I recall, that is not even possible in all cases.
> 
> You can report it at https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Flatex3%2Flatex2e%2Fissues&data=05%7C01%7Cross.moore%40mq.edu.au%7Cb835786ca79f4e5ce14408dab6052b6a%7C82c514c1a7174087be06d40d2070ad52%7C0%7C0%7C638022430579899924%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=7w90Ps8vKakYBSDJgH71vTwHFp2SRIbhVwT0x8nb6nQ%3D&reserved=0, but your
> document is very complicated. They may not be able to debug the
> problem. If there is any way you can cut it down to something smaller
> that still has the problem, that would surely help.
> 
>    And I cannot use dvips with this code because there is problem with
>    package babel.
> 
> I don't understand how babel plays into this. But if you're seeing a bug
> in babel, please report it at https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Flatex3%2Fbabel%2Fissues&data=05%7C01%7Cross.moore%40mq.edu.au%7Cb835786ca79f4e5ce14408dab6052b6a%7C82c514c1a7174087be06d40d2070ad52%7C0%7C0%7C638022430579899924%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=5PvuuGtHEiin8HoicpPasntzg8XkIsl%2FKwHh9MLUUUA%3D&reserved=0.
> 
> FWIW, when I run latex+latex+dvips+ps2pdf, I get a 295 page pdf in
> Russian that looks ok. Not that I know Russian or have any idea what I'm
> looking at :). 
> 
> I tried running dvipdfmx, but your .dvi has many PostScript specials, so
> that doesn't work. I don't know where they came from. But maybe if you
> tell whatever graphics/other package that you're using dvipdfmx, you
> could get a pdf out that way. --best wishes, karl.
>