quarto-dev / quarto-dev/quarto-cli

\boldsymbol rendered incorrectly to PDF default (using Lualatex) because unicode-math takes precedence

Open
#14,610 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Bug description

I was rendering a .qmd file into a PDF document when I found that \boldsymbol didn't work: the letters inside them are just ordinary, not bold.

However, rendering it to HTML would work perfectly; the \boldsymbols are rendered as bold characters.

I was using a separate install of TinyTeX (directly, without Quarto), whose path was manually added to Path.


A test of TinyTeX itself was done as follows: I write a separate .tex file:

\documentclass{article}
\usepackage{amsmath}

\begin{document}

$$
\boldsymbol{r} r
$$

\end{document}

and used xelatex test.tex AND lualatex test.tex to render it; the result is perfect, the first r is bold while the second is ordinary.

Also, directly using pandoc to convert to PDF file works perfect.

Steps to reproduce
---
title: "quarto boldsymbol test"
format:
    pdf:
        toc: false

latex-tinytex: true
---

# Title

$\boldsymbol{r} r$

$$
\boldsymbol{r} r
$$


I also tried using xelatex as PDF engine, which didn't work either.

I also tried latex-tinytex: false, which didn't work either.

I also tried manually adding amsmath by:

header-includes:
    - \usepackage{amsmath}

which didn't work.

Actual behavior

For example, in the .qmd file above, the rendered PDF file displays every r as ordinary letters, no bold.

Expected behavior

rs inside \boldsymbol should be bold.

Your environment
  • OS: Windows 11
  • Quarto: 1.9.37
  • TinyTeX:
    • tlmgr: tlmgr revision 78616 (2026-04-06 15:48:59 +0200)
    • xelatex: XeTeX 3.141592653-2.6-0.999998 (TeX Live 2026)
    • lualatex: This is LuaHBTeX, Version 1.24.0 (TeX Live 2026) Development id: 7724

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

Reproduce the issue with the provided .qmd example and compare it with the standalone test.tex using lualatex and xelatex. Trace the PDF rendering path and how unicode-math is included; done when \boldsymbol renders bold in Quarto PDFs without breaking the existing engines.

Written by the indexing model from the issue text.

Assessment

Tech stack
latex
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.