[Bug] Footnotes in project chapters are once again overwriting previous chapters' footnotes

[cbop-dev]

Description

Issue #45 seems to have reemerged, for me, on the Debian desktop (AMD) package, from at least version 2.1.0 onward (to 2.1.3). That is, in any project, when later chapters have footnotes with the same numbers (1, 2, 3...) as earlier chapters, the later footnotes overwrite the earlier chapters' notes in the output (including html and pdf). Can this be fixed again?

Reproducing

Create a new project with two markdown files. Add footnotes to each file, beginning numbering from 1, 2, 3...etc within each file. Export project and look at output. The notes of first file are overwritten by those of second.

Zettlr Version

Stable (most recent version)

Specify version

2.1.3

Your Platform

• Windows
• macOS
• Linux

Architecture

• Intel 64bit
• ARM 64bit

Operating System Version

Linux Mint 20.3 Cinnamon

Additional Information

No response

[boring-cyborg]

Thanks so much for opening up your first issue here on the repository! 🎉 We would like to warmly welcome you to the community behind the app! ☺️ We'll check in soon and have a look at your issue. In the meantime, you can check your issue and make sure it aligns with our contribution guidelines! Here's the comprehensive list:

Enhancements

An enhancement takes a feature and improves or alters its behaviour. Please make sure to argue how your proposition will aid non-technical text workers, and why it can't be emulated easily with other features or apps!

Feature requests

Feature requests introduce whole new features into the app. This requires a lot of work, so these might be turned down if the implementation costs supersede the benefits we expect to see from implementing it. Please do not be disappointed if that happens. It likely has nothing to do with your great request but simply with us and our missing resources!
You can of course always ask someone to implement this feature, because a PR with a working new feature has much higher chances of being merged! :)

Bug reports

Please note that one of the main reasons for why bug reports cannot be addressed is that there's not enough information for us to find and fix the bug you describe, so make sure you try to pinpoint the bug as close as possible.
The ideal bug report for us has two qualities:

1. The bug is always reproducible, at least within a certain context. 2. We know exactly what specifically goes wrong, and there is consensus on
   what should happen instead.

Please note that if you encounter behaviour that does not align with your expectations of what would happen, this might as well be simply intended behaviour and we need to simply clarify why the behaviour is the way it is. This is not to be considered a bug and such issues may be closed! Suggest an enhancement instead!
But now, have a great day and thank you again!

[nathanlesage]

Would you mind trying to add the following line to the corresponding defaults file (either HTML or PDF, etc.) in the assets manager?

file-scope: true

This issue should help precisely with that, see the Pandoc documentation: https://pandoc.org/MANUAL.html#option--file-scope

If that helps, I can integrate something like that in the defaults files so that other users won't notice any errors.

[cbop-dev]

Yes, setting file-scope: true in the defaults files fixed the problem. By default, this had been set to false in the two defaults files I checked, PDF and HTML. I had to change it manually for each file, but now it works.

Is there any reason not to have this set to true by default for each output type upon installation? Or at least have any given project automatically change it to true when exporting (since, by their very nature, projects involve more than one file)?

In any case, many thanks!

[nathanlesage]

Is there any reason not to have this set to true by default for each output type upon installation?

No, there is no reason. When I created the defaults files, I basically just chose some sensible defaults, but there were definitely judgmental errors, so I'm glad whenever something like this comes up so we can fix it gradually!