Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

amsart and itemize leads to infinite loop #17

Open
teepeemm opened this issue May 6, 2019 · 4 comments
Open

amsart and itemize leads to infinite loop #17

teepeemm opened this issue May 6, 2019 · 4 comments
Assignees
Labels
strucPDF transferred from old `strucPDF`package. Needs to be checked against accessibility

Comments

@teepeemm
Copy link

teepeemm commented May 6, 2019

In TeX Live 2017 on Windows 10, the following tex file

\documentclass{amsart}
\makeatletter
\providecommand{\@opargbegintheorem}{} % not defined in amsart?
\makeatother
\usepackage[tagged]{strucPDF}
\begin{document}
\begin{itemize}
\item some item
\end{itemize}
\end{document} % line 10

Leads to an infinite loop. The log file gets stuck repeating
Package strucPDF Warning: empty \PopStack? on input line 10.
infinitely often. It's ok with the article class.

@AndyClifton AndyClifton self-assigned this May 7, 2019
@AndyClifton
Copy link
Owner

AndyClifton commented May 7, 2019

Thanks for reporting this. Could you try this:

  1. Removing the command definition at the start, and then
  2. Adding some text between the \begin{document} and \begin{itemize}

.... and then compile? Could you confirm you still see the same bug?

If you do, could you also try with a more complete article? I've seen problems with shorter articles for some reason that I don't understand.

@teepeemm
Copy link
Author

teepeemm commented May 7, 2019

If I remove the \providecommand, then I get
! LaTeX Error: \@opargbegintheorem undefined.
at line 1176.

If I insert \lipsum before and/or after the itemize environment, I still get into an infinite loop of
Package strucPDF Warning: empty \PopStack?
on the \end{document} line.

If I insert \section{Section Title} between \begin{document} and \begin{itemize}, then it compiles without error.

Thanks for following up.

@AndyClifton
Copy link
Owner

AndyClifton commented May 7, 2019 via email

@teepeemm
Copy link
Author

teepeemm commented May 8, 2019

Unfortunately, I don't have convenient access to Acrobat Pro (and don't know how to check the tags there anyway). The main reason tagging has come up for me is that my institution is starting to use http://ally.ac/ with its learning management system to rate the accessibility of documents, and Ally complains bitterly if a pdf isn't tagged.

I did run across this problem with a realistic document that had maketitle, a line of text, and then a four item list. But if including a section title gets it to compile, then that does seem good enough.

@AndyClifton AndyClifton transferred this issue from another repository Sep 8, 2019
@AndyClifton AndyClifton added the strucPDF transferred from old `strucPDF`package. Needs to be checked against accessibility label Oct 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
strucPDF transferred from old `strucPDF`package. Needs to be checked against accessibility
Projects
None yet
Development

No branches or pull requests

2 participants