Merged
Conversation
ed85c99 to
338decd
Compare
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds support for footnotes in HTML. The DOM structure is based on Digital Publishing ARIA and also relatively similar to what Pandoc emits. To implement footnotes in a final step, the PR first sets up some infrastructure, which is separated into individual commits.
Currently, footnotes are always emitted at the very end of the document's
body. In the future, I want to expose a container element that can be placed by the user to customize the position (this element already exists, but is internal for now). This could feasibly also be supported in paged export. When the user emits their own html or body tag, footnotes are currently ignored, but in the future, the user would be expected to then also place their own footnote container.