-
Notifications
You must be signed in to change notification settings - Fork 335
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
Quarto Website: Using local fonts (Google Fonts) #4387
Comments
Can you provide a link to a full repo that causes this? Thanks. |
https://github.com/Klesel/QuartoIssueGoogleFonts Unfortunately, I was not able to reproduce the fact that the fonts are copies to |
Ok, there are a number of things going on here. Your repo has a few mistakes, but they're all easy to fix.
That does the trick for me locally. I'm going to go ahead and close this, but feel free to open if it doesn't solve your issue. |
I sent you a PR with the required fixes. |
@cscheid Your help is very much appreciated. That works perfectly. I would love to see this in the documentation! |
@Klesel I made a note of this example, yes. We have our plates full but it'll be there when we get to it. |
Bug description
Setting: Quarto Website using a theme.
Objective: I would like to avoid downloading google fonts via the google api
Idea: Storing the fonts locally and include them via a custom scss file
_quarto.yml
:light.scss
:In my environment, the fonts are still downloaded from the google api in the fonts folder:
/site_libs/bootstrap/fonts
This screenshot also shows that the api is still in use:
From a user perspetive, it would be most helpful to have a variable that ensures that no font is used via an api. Any other approach to ensure that only local fonts are used would likewise be appreciated.
As a side-note: This is particularily relevant in Germany, because there is a legal issue using google fonts that are included via the API. Therefore, this issue should be relevant for a larger group of users.
I raised this issue here.
My environment:
Checklist
The text was updated successfully, but these errors were encountered: