Skip to content
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

Section/Subsection Heading Footnotes Duplicated #110

Closed
spidersouris opened this issue Nov 1, 2024 · 1 comment · Fixed by #132
Closed

Section/Subsection Heading Footnotes Duplicated #110

spidersouris opened this issue Nov 1, 2024 · 1 comment · Fixed by #132
Labels
bug Something isn't working upstream

Comments

@spidersouris
Copy link

Description of Issue

Defining a footnote on a section/subsection heading (level 1 or 2) duplicates it.

Minimal Example

#import "@preview/touying:0.5.2": *
#import themes.simple: *

#show: simple-theme.with(aspect-ratio: "16-9")
#show heading: it => text(fill: red, smallcaps(it))

= Title#footnote("this is a duplicated footnote")

== First Slide#footnote("this is another duplicated footnote")

=== 123#footnote("this footnote is fine though")

Hello, Touying!

Hello, Typst!

Current Behavior

It seems that footnotes are applied once to the section/subsection title (in the header) and once to the slide title? The screenshot below shows that footnote 1 first appears on page 2 next to the "First Slide" section title, and a second identical footnote (numbered 2) appears on the very first slide next to "Title".

image

@OrangeX4 OrangeX4 added bug Something isn't working upstream labels Nov 2, 2024
@OrangeX4
Copy link
Member

OrangeX4 commented Nov 2, 2024

There is currently no good solution for this, but try not to use footnote in the heading.

@OrangeX4 OrangeX4 linked a pull request Dec 5, 2024 that will close this issue
@OrangeX4 OrangeX4 closed this as completed Dec 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working upstream
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants