quarto-dev / quarto-dev/quarto-cli

The `thanks` metadata is silently ignored in Typst format

Open
#14,484 1 comment 0 reactions 1 assignee View on GitHub

@gordonwoodhull is already working on this.

Since May 5, 2026.

enhancement typst
Dominant language
JavaScript
Stars
6k
Forks
458
Avg merge
1d 9h
Merged PRs (30d)
41

Description

I have:
  • searched the issue tracker for similar issues
  • installed the latest version of Quarto CLI
  • formatted my issue following the Bug Reports guide
Bug description

When rendering a Quarto document with format: typst, the thanks content does not appear in the output PDF, while seeing superscript * on the title.

After investigating with keep-typ: true, it looks like Quarto passes the thanks value correctly into the generated .typ file, but the title block renders the footnote inside a place(float: true, scope: "parent") container. Typst does not currently render footnote contents correctly in that situation (typst/typst#5765)

This seems to make Quarto's documented thanks feature non-functional for Typst output.

Steps to reproduce
---
title: Test
thanks: "This should appear as a footnote"
format: typst
---

Hello.
Actual behavior

No footnote appears in the rendered PDF. The title is shown with a * marker.

Expected behavior

A footnote marked with * should appear at the bottom of the title page.

Your environment
  • IDE: VS Code
  • OS: macOS (26.3.1)
Quarto check output
quarto check
Quarto 1.9.37
[✓] Checking environment information...
      Quarto cache location: /Users/kazuharu/Library/Caches/quarto
[✓] Checking versions of quarto binary dependencies...
      Pandoc version 3.8.3: OK
      Dart Sass version 1.87.0: OK
      Deno version 2.4.5: OK
      Typst version 0.14.2: OK
[✓] Checking versions of quarto dependencies......OK
[✓] Checking Quarto installation......OK
      Version: 1.9.37
      Path: /Applications/quarto/bin

[✓] Checking tools....................OK
      TinyTeX: v2026.03.02
      Chromium: 869685
            (Chromium is outdated. Run "quarto uninstall chromium" then "quarto install chrome-headless-shell")
      Chrome Headless Shell: (not installed)
      VeraPDF: (not installed)

[✓] Checking LaTeX....................OK
      Using: TinyTex
      Path: /Users/kazuharu/Library/TinyTeX/bin/universal-darwin
      Version: 2026

[✓] Checking Chrome Headless....................OK
      Using: Chrome found on system
      Path: /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
      Source: MacOS known location

[✓] Checking basic markdown render....OK

[✓] Checking R installation...........OK
      Version: 4.5.3
      Path: /Library/Frameworks/R.framework/Versions/4.5-arm64/Resources
      LibPaths:
        - /Users/kazuharu/Library/R/arm64/4.5/library
        - /Library/Frameworks/R.framework/Versions/4.5-arm64/Resources/library
      knitr: 1.50
      rmarkdown: 2.29

[✓] Checking Knitr engine render......OK

[✓] Checking Python 3 installation....OK
      Version: 3.14.4
      Path: /opt/homebrew/Cellar/jupyterlab/4.5.7/libexec/bin/python
      Jupyter: 5.9.1
      Kernels: julia-1.11, julia-1.10, julia-1.12, nbstata

      NOTE: No Jupyter kernel for Python found

[✓] Checking Julia installation...

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.