Typst: #refs div placement not honored; stray 'Referenties' heading inside appendix

Open
#1,105 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
rust

Research direction

Start by reproducing the reported PDF with q2 0.42.0, Typst 0.15.1, and Pandoc 3.13 using the Quarto document in the issue. Trace how format: typst handles the #refs div and heading placement alongside appendices, then compare with the intended Typst citation behavior. Done when the bibliography appears in the intended location without the stray numbered “Referenties” heading in the appendix.

Written by the indexing model from the issue text.

Description

With format: typst, a ::: {#refs} div doesn't seem to control where the bibliography goes:

---
format: typst
number-sections: true
bibliography: refs.bib
---

# Inleiding

Text [@smith2020].

# Referenties {.unnumbered}

::: {#refs}
:::

# Bijlage A {.appendix}

Aanvullend materiaal.

In the PDF, "Referenties" is empty. A heading "3.1 Referenties" appears inside "3 Bijlage A", and the list itself appears at the end under a separate "Bibliografie" heading (Typst's own bibliography).

I'm not sure what the intended behavior is. It may be inherited from Quarto 1's Typst output (Typst-native citations), or my markup may not be how appendices and refs are meant to combine for Typst. The duplicated "Referenties" heading inside the appendix looks unintended, though. The appendix is also numbered "3", not "A"; that may be expected for Typst.

q2 0.42.0, Typst 0.15.1, Pandoc 3.13, Windows 11.

Dominant language
Rust
Stars
302
Forks
22
Avg merge
5h 2m
Merged PRs (30d)
213

Getting set up

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.

More from quarto-dev/q2

All issues in quarto-dev/q2

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.