quarto-dev / quarto-dev/quarto-cli

Extra dot in the number of the highest section heading in qmd docx

Open
#10,441 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Bug description

When using number-sections: true, qmd docx produces an extra dot after the number of the Heading 1, which does not occur in Rmd word_document

Steps to reproduce

In qmd

---
title: "Untitled"
format: 
  docx:
    number-sections: true
---

# Heading 1

## Heading 2

### Heading 3

and in Rmd

---
title: "Untitled"
output: 
  word_document:
    number_sections: true

---


# Heading 1

## Heading 2

### Heading 3
Expected behavior

1 Heading 1
1.1 Heading 2
1.1.1 Heading 3

Actual behavior
  1. Heading 1
    1.1 Heading 2
    1.1.1 Heading 3
Your environment

RStudio 2024.04.2
Windows 11

Quarto check output
Quarto 1.5.55
[>] Checking versions of quarto binary dependencies...
      Pandoc version 3.2.0: OK
      Dart Sass version 1.70.0: OK
      Deno version 1.41.0: OK
      Typst version 0.11.0: OK
[>] Checking versions of quarto dependencies......OK
[>] Checking Quarto installation......OK
      Version: 1.5.55
      Path: C:\Program Files\Quarto\bin
      CodePage: 65001

[>] Checking tools....................OK
      TinyTeX: v2024.01
      Chromium: (not installed)

[>] Checking LaTeX....................OK
      Using: TinyTex
      Path: 
      Version: 2023

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

[>] Checking Python 3 installation....(None)

      Unable to locate an installed version of Python 3.
      Install Python 3 from https://www.python.org/downloads/

[>] Checking R installation...........OK
      Version: 4.3.3
      Path: C:/PROGRA~1/R/R-4.3.3
      LibPaths:
        - C:/win-library
        - C:/Program Files/R/R-4.3.3/library
      knitr: 1.48
      rmarkdown: 2.27

[>] 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.

Research direction

Render the supplied qmd example with docx and number-sections enabled, then compare its Heading 1 numbering with the expected output and the Rmd word_document result. Trace the Quarto CLI/Pandoc docx heading-numbering path; done means the extra dot is removed while the 1.1 and 1.1.1 headings remain correct.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.