Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Typst: image size in px is not converted when the image has fig-alt

Aperta Adatta ai principianti
#14,947 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
75/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
lua
Ambito
cli, documentation

Direzione di ricerca

Il bug si trova in src/resources/filters/quarto-post/typst.lua, righe 218-225 e 262-273. Inizia leggendo il codice del filtro per vedere come gestisce le immagini con fig-alt. La correzione probabilmente comporta la conversione delle unità px in pollici utilizzando PANDOC_WRITER_OPTIONS.dpi, in modo simile a come vengono gestiti i numeri semplici. Testa creando un file .qmd minimale con un'immagine che ha fig-alt e una dimensione in px, quindi esegui quarto render per verificare che il file .typ generato non contenga più 'px'.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

accessibility bug typst
Bug description

When I render to Typst, an image with fig-alt keeps its size in px. Typst has no px unit, so compiling the document fails with invalid number suffix: px. The same image without fig-alt renders fine, because Quarto converts its size to inches.

The cause is in the Typst filter, quarto-post/typst.lua. When an image has alt text, the filter doesn't pass it on to Pandoc. It writes the Typst image() call itself as a RawInline and copies the height and width values across unchanged. The filter does convert sizes before that, but only when they're plain numbers. tonumber("200px") returns nil, so 200px ends up in the Typst code as it is.

This is where the filter builds the image() call for an image with alt text:

An image without alt text goes through Pandoc's Typst writer instead, and that writer turns pixel sizes into inches:

Sizes in % still work with fig-alt, because Typst understands %.

Checked against Pandoc

I also ran the same image through Pandoc on its own, and Pandoc isn't the cause. The Pandoc 3.10 bundled with Quarto converts the size and writes the alt text correctly:

printf 'A ![](https://quarto.org/quarto.png){height="200px" alt="Quarto logo."} b\n' | quarto pandoc -f markdown -t typst
# #box(image("https://quarto.org/quarto.png", height: 2.08333in, alt: "Quarto logo."))

A comment in the filter says the raw image() call is a workaround, because Pandoc used to leave alt text out of Typst output (jgm/pandoc#11394). Pandoc 3.10 writes alt: itself now, so the workaround might not be needed any more. For the moment, it's the code path that causes this bug.

Steps to reproduce
---
format: typst
keep-typ: true
---

![](https://quarto.org/quarto.png){height="200px"}

![](https://quarto.org/quarto.png){height="200px" fig-alt="Quarto logo."}
Actual behavior

The generated .typ file has these two lines:

#box(image("t3_files/mediabag/quarto.png", height: 2.08333in))
#box(image("t3_files/mediabag/quarto.png", alt: "Quarto logo.", height: 200px))

Typst then stops with this error:

error: invalid number suffix: `px`
Expected behavior

I'd expect the image with fig-alt to have its size converted just like the one without it:

#box(image("t3_files/mediabag/quarto.png", alt: "Quarto logo.", height: 2.08333in))

I can see two ways to fix it. The filter could convert px values to inches with PANDOC_WRITER_OPTIONS.dpi, as it already does for plain numbers. Or, now that Pandoc 3.10 writes the alt text itself, the filter could let Pandoc handle these images as well.

Your environment

I'm on macOS. The bug happens with Quarto 1.10.18 and with the current main branch at commit 03f0fdf586b066ffa81ebefa55e5dad21e08bec0.

Quarto check output

This output comes from the development build I used to confirm the bug on main.

[✓] Checking environment information...
      Quarto cache location: /Users/mcanouil/Library/Caches/quarto
[✓] Checking versions of quarto binary dependencies...
      Pandoc version 3.10.0: OK
      Dart Sass version 1.101.0: OK
      Deno version 2.7.14: OK
      Typst version 0.15.1: OK
[✓] Checking versions of quarto dependencies......OK
[✓] Checking Quarto installation......OK
      Version: 99.9.9
      commit: 03f0fdf586b066ffa81ebefa55e5dad21e08bec0
      Path: /Users/mcanouil/Projects/quarto-dev/quarto-cli/package/dist/bin

[✓] Checking tools....................OK
      TinyTeX: v2026.07
      Chrome Headless Shell: (not installed)
      VeraPDF: (not installed)

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

[✓] Checking Chrome Headless....................OK
      Using: Chrome from QUARTO_CHROMIUM
      Path: /Applications/Brave Browser.app/Contents/MacOS/Brave Browser

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

ℹ R version 4.6.1 (2026-06-24)
! Config '~/.Rprofile' was loaded!
[✓] Checking R installation...........OK
      Version: 4.6.1
      Path: /Library/Frameworks/R.framework/Versions/4.6/Resources
      LibPaths:
        - /Users/mcanouil/Projects/quarto-dev/quarto-playground/renv/library/macos/R-4.6/aarch64-apple-darwin23
        - /Users/mcanouil/Library/Caches/org.R-project.R/R/renv/sandbox/macos/R-4.6/aarch64-apple-darwin23/46003b10
      knitr: 1.51
      rmarkdown: 2.31

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

[✓] Checking Python 3 installation....OK
      Version: 3.9.6
      Path: /Library/Developer/CommandLineTools/usr/bin/python3
      Jupyter: (None)

      Jupyter is not available in this Python installation.
      Install with python3 -m pip install jupyter

      There is an unactivated Python environment in .venv. Did you forget to activate it?

[✓] Checking Julia installation...
Lingua principale
JavaScript
Stelle
6k
Fork
458
Merge medio
1g 3h
PR unite (30g)
54

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di quarto-dev/quarto-cli

Tutte le issue di quarto-dev/quarto-cli

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.