Relative font-paths not working, but absolute font-paths are working #13742
Replies: 3 comments 7 replies
-
|
I should also add: I've already tried shifting the Interestingly, quarto finds > tree -d _extensions
_extensions
βββ lirneasia
βββ assets
βββ fonts
βΒ Β βββ aptos
βΒ Β βββ montserrat
βββ logos |
Beta Was this translation helpful? Give feedback.
-
|
When I do But I suspect the issue is from running this document from inside a nested folder from your root. With a repo in the project root, I bet you wouldn't have errors. Using But I think this is an issue we need to see if we can fix, or if this is a limitation of typst (like with LaTeX where resources needs to be placed outside of _extensions) |
Beta Was this translation helpful? Give feedback.
-
|
Just a comment to subscribe, since I'm facing a similar issue (as documented here: https://github.com/orgs/quarto-dev/discussions/12638#discussioncomment-14895562). |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
-
Description
I have an custom extension in which I use font-paths. If I use an absolute font-path, the fonts get picked up. If I use a relative font path, they don't.
The CI fails in this repo. (If anyone has any other comments about how that repo is organized, or the Typst template I've written, or anything else, I'm very happy to receive feedback.)
I found this issue, but it doesn't seem to explain what's going on: #12695
The output of
quarto renderseems to be okay, but still the fonts don't get recognized.The error:
If I uncomment the absolute path, the fonts get recognized when I do
quarto render:Beta Was this translation helpful? Give feedback.
All reactions