Closed hvoss49 closed 2 years ago
I confirm the bug.
Minimal test case: seems to be enough to load babel
after amsmath
to trigger the issue
\documentclass{article}
\usepackage{amsmath}
\usepackage{babel}
\begin{document}
test
\end{document}
Ah, that explains why I had no problem with another document!
@hvoss49
If you are on texlive and you have tlmgr configured to take backups, tlmgr restore babel 62007
can temporarily fix the issue for you by reverting to a previous version of babel.
thanks, I already did this.
thanks, I already did this.
I never recognize github usernames! Still hope the advice can be useful to others landing on this page!
Another possibility for those not having a backup can be to keep a local copy of luababel.def
in the current project. For convenience, I have attached it below (you need to get rid of the final .txt
extension that is there just to make github happy).
Found. A missing line with an \fi
, which I’ve deleted accidentally. I’ll upload a fix asap.
That was quick! Thanks!
@jbezos Javier, given that you recently made a number of fixes in that space it might pay off to set up a few regression tests files just testing various combination of package loads; I guess many of the recent issues might have been found through simply testing a few of that combinations and ordering
@FrankMittelbach The actual problem is combinations sometimes tend to infinite. I have more than one thousand test files, including the sample files for tlc2 tested with several combinations of babel options, which leads to several thousand tests. I’m running them right now. I don't know how it happened, but it happened.
I know :-) but still a few key permutations might help. Note that most of the test if done with the typical regression setup do not show errors if they happen during loading unless you explicitly tell them so.
With latest update and running lualatex I get
It is from a bigger project, so I cannot easily produce a minimal example. And with another document there is no problem.