quarto-dev / quarto-dev/quarto-cli

For all length specifications, use proper units of measurement

Open
#2,463 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Bug description

For all user-facing length specifications, please refrain from supporting dimensionless numbers implied to be inches.

Do support numbers only when combined with explicit units of measurement, such as 10in, 17cm, or 150mm.

(Including, but by no means limited to page-width, fig-width, fig-height …)

Please do follow the examples of TeX/LaTeX, pandoc, and pretty much every text processor (MS Word, LibreOffice, Pages, etc.) there is in this respect.

Checklist
  • Please include a minimal, fully reproducible example in a single .qmd file? Please provide the whole file rather than the snippet you believe is causing the issue.
  • Please format your issue so it is easier for us to read the bug report.
  • Please document the RStudio IDE version you're running (if applicable), by providing the value displayed in the "About RStudio" main menu dialog?
  • Please document the operating system you're running. If on Linux, please provide the specific distribution.

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

Start by creating the requested minimal, fully reproducible example in a single .qmd file, covering user-facing length specifications such as page-width, fig-width, and fig-height. Trace how these specifications accept dimensionless values, then verify that the affected cases require explicit units such as in, cm, or mm.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.