Skip to content
Discussion options

You must be logged in to vote

Your .font call is right. The catch is how quarkdown loads a font by name from the system. It becomes

@font-face { font-family: '<id>'; src: local('Alegreya'); }

(CssFontFacesImporter in quarkdown-html), and CSS local() matches a font's full name or PostScript name, not its family name. For the Google Fonts builds of your two fonts, those names are:

Font file Family Full name PostScript name
Alegreya[wght].ttf Alegreya Alegreya Regular Alegreya-Regular
SourceCodePro[wght].ttf Source Code Pro ExtraLight Source Code Pro ExtraLight Regular SourceCodePro-ExtraLight

So local('Alegreya') and local('Source Code Pro') match nothing, and the browser falls back to the theme's font witho…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by iamgio
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants