quarto-dev / quarto-dev/quarto-cli

Fenced div problem: listing with `date-format: long` and `lang: de`

Open
#13,642 6 comments 0 reactions 1 assignee View on GitHub

@cderv is already working on this.

Since Nov 4, 2025.

bug listings
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

I recently upgraded to Quarto 1.7.32.
I have a quarto project with the language set to German in the _quarto.yml. When I use a listing with date-format: long, I get multiple warnings like this one:

[WARNING] Div at line 12 column 1 unclosed at line 128 column 1, closing implicitly.
WARNING
The following string was found in the document: :::
This usually indicates a problem with a fenced div in the document. Please check the document for errors.

The document ist rendered, but the page with the listing looks weird and has multiple ":::" displayed on the page.

Steps to reproduce

GitHub repository containing a reproducible example

Actual behavior

No response

Expected behavior

No response

Your environment

No response

Quarto check output

Quarto 1.7.32
[>] Checking environment information...
[>] Checking versions of quarto binary dependencies...
Pandoc version 3.6.3: OK
Dart Sass version 1.85.1: OK
Deno version 1.46.3: OK
Typst version 0.13.0: OK
[>] Checking versions of quarto dependencies......OK
[>] Checking Quarto installation......OK
Version: 1.7.32
CodePage: 1252

[>] Checking tools....................OK
TinyTeX: v2025.08.02
Chromium: (not installed)

[>] Checking LaTeX....................OK
Using: TinyTex
Version: 2025

[>] Checking Chrome Headless....................OK
Using: Chrome found on system
Source: Windows Registry

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

[>] Checking Python 3 installation....OK
Version: 3.13.6
Jupyter: 5.9.1
Kernels: python3

[>] Checking Jupyter engine render....OK

[>] Checking R installation...........OK
Version: 4.5.1
knitr: 1.50
rmarkdown: 2.30

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

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.