-
Notifications
You must be signed in to change notification settings - Fork 36
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
cleveref
now refers to appendices as sections
#362
Comments
Try this (or switch to something else, e.g. zref-clever)
|
That does it, thanks. Unfortunately, the source markdown document is being compiled to latex by pandoc with the pandoc-crossref filter, so am forced to use |
Looking through the |
Same issue with other
in which case @u-fischer Is this something that can be fixed, or is the official stance now that EDIT: Again, I only found your tex.SE answer after posting this... https://tex.stackexchange.com/questions/730148/cref-refers-to-lemmas-as-theorems |
@clason without complete example I can't test, but probably you can fix it with https://tex.stackexchange.com/a/730164/2388.
Well the only one who can give an official stance about cleveref is its maintainer. So contact him and ask. Generally, we are trying to fix issues with cleveref and add firstaid code for it. But cleveref has 8000 lines of code. It redefines various public and internal definitions from a large number of packages and from the kernel and there is no testsuite one can use to check for problems so some fixes are still missing.
well it would be nice if there were a replacement that does not patch everything but makes use of the new interfaces provided by LaTeX like the hooks and the properties. But someone would have to tackle the task to do that. |
Yes, indeed! (Sorry, I really should get in the habit of checking tex.se before Github; open source work has ruined me in that regard...)
Of course (although I doubt that I would get an answer if you don't...) My question was more along the lines of "is the team close to (very understandably) throwing in the towel on this and saying 'if you want to use an abandoned and outdated package, you should use an outdated kernel"? But it sounds like you're not quite there yet (and I cannot stress enough how appreciated your enormous efforts are), so I'll postpone the significant investment for my templates still.
Oh, for sure, that is not on your plate at all. (Actually all I'm hoping for is for someone to write a cref-compatible wrapper for |
Well I don't know what is missing or is not cref compatible, but if you make a list or examples you could ask the zref-clever author. |
Basically, I would love to have a package I can import instead of But I've taken enough of your time already (and thanks)! |
I can confirm this issue. I've gone through the commit list. The problem does not occur in commit 48bdab913d4e8a2fcfe229ef6b5302f6fd22b644 (docu) but in 697ed67f60dbf235d7843ec43e6f09114e707a81 (adapt nameref to new label handling) so the problem was probably introduced in the latter commit.
|
I know which changes where made in hyperref and in the kernel.
the only one who can give an official stance about the status of cleveref is its maintainer. So ask him.
well as I wrote above and in the tex.sx answer, the easiest and best currently is to set the alias explicitly through a hook. As long as the maintenance status is so vage it is very difficult to work on a fundamental solution. |
On my system I not only had to include
then cleveref works as expected, without anything else fancy in the preamble. I tried to migrate to zref-clever once before, but at that time it wasn't yet working in texlive (which my collaborators were using) due to the kernel version being too old. Maybe now is the time to try again. It's pretty clear that cleveref isn't going to see updates (it's been 7 years). |
Using
hyperref
2024-11-05 v7.01l with LaTeX 2024-11-01 and the example file:cleveref
now refers to sections in the appendix assection
instead ofappendix
. I suspect this is related to the issue with\refstepcounter
and related to latex3/latex2e#1393, #360, #361 and fffd2e0.The text was updated successfully, but these errors were encountered: