I’m working on a foundry website. Have two families so far, put them in a cms in webflow so they get the exact same treatment, but have some options as far as content and size goes on the backend. They’re both variable, ttf exports, yet one renders tack sharp (Cause), and the other sort of blurry (Wilder), especially in bigger sizes. Any idea what this could be? Some export setting on my part? Safari works fine, it’s Chrome on Mac that’s behaving weird for me…
I can’t immediately find any difference in your implementation of the files in your CMS and/or their treatment in CSS. Looks like something to do with your export, but I have never encountered this issue before. What file format(s) are you using to implement your fonts?
Thanks Sebastian, they’re both variable ttf’s, i always export the same way so not sure what’s different between the files. I’ll add the link to both fonts below.
Rasterizers sometimes render for one size and then scale up or down a notch. And when they do, that’s what it looks like in the screenshot Sebastian posted.
Cant’t really find any sources on how to fix rasterizers on web. Any idea what to do here? And why is it one of them behaves normal, and the other one doesn’t?
Tried on Font Gauntlet to see (and also compare to something similar i.e. ABC Favorit) if there was any difference from your site but there is definitely something wrong.
Did anything change with your UPM or is there some other parameter checked on your export?
Even trying to open the TTF gives this error:
**The document “BEWilderVariableVF.ttf” could not be opened. Error while reading the document: /Users/Downloads/BEWilderVariableVF.ttf**
**(*** -[NSSubrangeData subdataWithRange:]: range {808, 1703244} exceeds data length 6848)**
I haven’t modified the UPM, fontbakery has some errors, but can’t make much of it. I do see something about nested components, but not sure where i’d use that…
Ok so here is the issue…or at least the fix. If you set the glyph “chains” to non-export then the text renders fine. It has something to do with it not being a closed outline.
Not sure why these icolor layers showed up, didn’t notice those. Maybe it’s because it expects an emoji? Deleting them did indeed fix it, thank you so much for helping out, guys!
