[JFWooten4]

Summary

• Use {key} instead of {{key}} to insert an already-assigned Markdown footnote number into prose, without creating a new citation or changing its numbering.
• Preserve the clickable link to the numbered footnote and the normal [^key] citation/definition syntax.
• Keep legacy double-braced expressions literal, rather than inadvertently rendering {{key}} as {7}.
• Update the README and regression tests for the new syntax, including references before their citation, repeated citations, whitespace, unresolved names, and end-to-end PDF generation.

Why simplify the syntax?

I originally used two pairs of braces to make note-number references stand out visually in raw Markdown. That distinction was useful when scanning the text as a human, but it is not necessary when a machine resolves and replaces the placeholders. A single pair of braces is simpler to type, read, and maintain, while the named reference still unambiguously identifies the assigned footnote number.

Example

The first proposition.[^smith]

See supra note {smith}.

[^smith]: Smith v. Jones, 123 U.S. 456.

If smith is assigned note 7, the second paragraph renders “See supra note 7.” with 7 linked to the actual footnote.

Code-block safety

Footnote numbers must come from actual prose citations, not examples of Markdown syntax. The compiler now preserves literal {key} placeholders, [^key] citations, and [^key]: definitions inside fenced code blocks. Both backtick and tilde fences are recognized, including longer delimiters. Inline backtick code spans are also protected from interpolation and citation numbering. This is enforced when extracting definitions, assigning numbers, rendering both PDF modes, and grouping endnotes by section.

Regression tests cover fenced code, inline code, longer backtick/tilde fences, preserved code-only definitions, and correct endnote sections.

Compatibility and verification

This is an intentional source-syntax change: existing documents that use {{key}} must change those references to {key}. Such legacy expressions remain visible rather than being half-interpolated.

Verified the committed tree differs from main, and reviewed the three-file diff. Added regression coverage and performed focused fence/inline-code helper smoke checks, but the full Python test suite was not executed in this environment.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
pdf	Ready	Preview	Oct 16, 2026 12:25am UTC