-
-
Notifications
You must be signed in to change notification settings - Fork 101
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
Reseting the footnote counter with each page #1018
Comments
Hmmm. This is probably an issue with |
Unfortunately, I don't have a minimalist example, this was part of a book which I can't share excerpts from. I will try to find an example though. |
If you can't narrow it down, load the debug package and disable pushback at the start of your document:
If that works, we know where the problem is. |
@simoncozens tried with your suggestion, sorry to report that it didn't work. |
@IsaZ Don't be too sorry, in a round-about way that is actually good news. If the bug is not in |
I haven't replicated the issue you showed yet, but there is a related issue in the opposite direction that will take some fixing. When a line gets shaped but doesn't fit onto the page and gets postponed to the next page, it might already have the footnote counters in it. This makes sense and we have no way to backtrack the counter and re-fill the node content with new values before shaping on the new page. The problem looks something like this:
|
Coming back to this issue, I got it wrong, so I fixed the report above. |
Thanks for the update. I'll put my thinking cap on again and see where we are at with this. |
Resetting the counter in
newPage
of a book class kind of works, but in some cases, the footnote counter is resetbeforelate in the next new page, even though the footnote itself is in the right page; something like this:Is it possible to do some kind of rerun to fix the numbers? similar to what is done in
tableofcontents
.EDIT: I previously got things mixed up, so I fixed this issue report.
MWE from @alerque below #1018 (comment)
The text was updated successfully, but these errors were encountered: