Add native footnote authoring and lookup - #1616
Draft
pseudosavant wants to merge 1 commit into
Draft
pseudosavant wants to merge 1 commit into
pseudosavant wants to merge 1 commit into
Conversation
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
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.
Add native footnote creation and lookup, with precise reference placement and editable note content.
Document.add_footnote(after=run, text=...)inserts a separate reference run without changing adjacent text or formatting.Document.footnotesexposes ordinary notes, andRun.footnote_idsexposes existing reference IDs. Notes support the existing block-container and run APIs.The implementation registers a typed footnotes story part, creates separator entries, reserves existing IDs, preserves note styles and numbering settings, and validates body or table-cell reference locations before adding package structures. It does not add endnotes, field-based reuse, note deletion, or pagination controls.
Related to #1 and the broader proposal in #1392. This draft offers a narrower creation and lookup API for discussion. It is based directly on upstream master and contains no fork packaging or other feature commits.
Validation: