Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Omit lualatex as pdf-engine #51

Open
SvonGrebmer opened this issue Feb 4, 2025 · 1 comment
Open

Omit lualatex as pdf-engine #51

SvonGrebmer opened this issue Feb 4, 2025 · 1 comment
Assignees
Labels
in discussion Details need to be fleshed out before implementation

Comments

@SvonGrebmer
Copy link
Member

I am curious to hear the reasoning behind using lualatex as explicit pdf-engine - can thing in the yaml be omitted so that defaults are used?

@fkohrt
Copy link
Member

fkohrt commented Feb 11, 2025

The everyday user definitively won't notice a difference. I still think using luaLaTeX is better than XeLaTeX (which Quarto currently uses by default) or pdfLaTeX (which rmarkdown uses) for various reasons:

  • the current accessibility improvements (i.e., creating tagged PDFs for blind users) happen for luaLaTeX and pdfLaTeX (but not XeLaTeX)
  • XeLaTeX is not actively developed anymore
  • some of the optional features in Pandoc's templates are only supported for luaLateX (e.g., selective ligature suppression)
  • Font expansion by the TeX package microtype is not supported for XeTeX

Some other reasons are also documented at quarto-dev/quarto-cli#11321 and Quarto will likely default to luaLaTeX in the future.

The major drawback probably is speed, as luaLaTeX is not known for its speed.

@fkohrt fkohrt added the in discussion Details need to be fleshed out before implementation label Feb 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in discussion Details need to be fleshed out before implementation
Projects
None yet
Development

No branches or pull requests

2 participants