Open davelab6 opened 3 years ago
I agree that'd fix the symptom, but would falsely suggest these characters are in the picked font when they're not.
The tester showing tofu instead of text sounds like a feature to me, not a bug :-) At least in the absence of a "fallback text" based on what the font does support.
I have a rough prototype for dropping multiple fonts in the fondue. If priority would be given to the font with the Unicode range of the font's name (Latin in case of Google Fonts' variable fonts), they can show the font name as intended on the first "tab".
Another option would be to have a clear fallback font in place, instead of tofu.
So, options:
@davelab6 Do any of those options appeal to you?
The beta offers Google Fonts split by subset, but when loading an subset other than
latin
, the preview defaults don't work, the family name can't be rendered in itself, etc. So it might be worth loading both latin and the other requested font, so that the latin is available on the page, even though the data isn't about it.