Add Typst fontPaths option #1791
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
domenkozar
reviewed
Mar 24, 2025
|
Now it puts the actual package path into the example, which is unexpected *Example:*
` [ "\/nix/store/pbcb7j89fggfmjafzplcpylvksay4v9q-roboto-2.138/share/fonts/truetype "] ] ` |
|
Oh, the dollar sign should be escaped with |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In order to make some fonts available to Typst, the latter supports the
TYPST_FONT_PATHSenvironment variable. Sure, fonts can be made available by simply adding them to thepackages. However, doing so results in Typst seeing them as system fonts, so you can't really know if it mistakenly chooses a font that is installed on your computer instead. Setting them viaTYPST_FONT_PATHS, in combination with running Typst with the--ignore-system-fontsflag, allows for a fully reproducible build.