quarto-dev / quarto-dev/quarto-cli

mermaid gantt diagram ignores language setting

Open
#6,970 8 comments 0 reactions 1 assignee View on GitHub

@cscheid is already working on this.

Since Sep 24, 2023.

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

Description

Bug description

When I setup a quarto document to use danish, and embed a mermaid gantt diagram, the html rendition of the gantt diagram contains dates in english.

Steps to reproduce
---
date: 2023-10-01
date-format: "D. MMM."
lang: da
---
```{mermaid}
gantt
  excludes weekends
  tickInterval 1month
  axisFormat %e. %b.

  section All
  Event: 2023-09-01, 2m
  Event: 2023-10-01, 2m
```
Expected behavior

Lower right corner of rendered gantt diagram should say "1. okt."

Actual behavior

Lower right corner of rendered gantt diagram should say "1. Oct."

I.e. capitalized and with "c" instead of "k" as in danish "oktober".

Your environment
  • IDE: none
  • OS: Linux
Quarto check output
$ quarto check
Quarto 1.4.376
[✓] Checking versions of quarto binary dependencies...
      Pandoc version 3.1.8: OK
      Dart Sass version 1.55.0: OK
      Deno version 1.33.4: OK
[✓] Checking versions of quarto dependencies......OK
[✓] Checking Quarto installation......OK
      Version: 1.4.376
      Path: /opt/quarto/bin

[✓] Checking tools....................OK
      Chromium: 869685
      TinyTeX: (not installed)

[✓] Checking LaTeX....................OK
      Using: Installation From Path
      Path: /usr/bin
      Version: 2023

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

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

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

[✓] Checking R installation...........(None)

      Unable to locate an installed version of R.
      Install R from https://cloud.r-project.org/

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.