Open Panogen opened 1 year ago
AFAIK it happens all the time in rendering of otf fonts and is not related to fontmake; most of font engineers generate otf output format just to give access to cubic bezier outlines of the glyphs for those users who want to do typographic edits.
Are you testing this only on Windows? OTF rendering there heavily depends on the application (specifically which part of Windows is used to draw text).
I have a UFO source which I am trying to export using
fontmake
. Thettf
looks great, but theotf
looks horrendous! At small sizes, not only is it greyscale (which I never specified—thettf
has proper subpixel rendering) but it is pixelated and looks way heavier than it should. I would just run withttf
, but I feel likeotf
, being more modern, should be the better of the two! I would prefer to useotf
anyway because the filesize is smaller and I drew the font using cubic curves, meaning the quadratic conversion is at play with thettf
.This screenshot shows: (left) TTF export with![sorazorafuzz](https://user-images.githubusercontent.com/73259774/215369904-efbcbc1b-946a-4ae1-b672-6c479e1ae98d.png)
fontmake
, (middle) OTF export withfontmake
, and (right) OTF export from FontForge.The FontForge OTF export used to look like the
However, it is still in greyscale in the font viewer, which isn't right. I also feel that removing this information must be detrimental to the rendering in some way.
fontmake
OTF export, but I fixed the issue by manually setting StdHW, StdVW, StemSnapH and StemSnapV (they were previously "guessed" by FF). Mysteriously, removing these values from fontinfo.plist in the generated UFO improves it significantly:Another thing I noticed is that all of the OTFs become a dark mess when rendered at smaller and smaller ppem sizes, even with the stem-snap values removed:
but the TTF seems to retain a more sensible (and consistent) color at the same size (ignoring the bold text—the font currently only has regular weight):
This is even more apparent in apps like LibreOffice, with the difference being visible even at normal reading sizes.
Are these problems just inherent to
otf
? Is this how it's supposed to be? Am I doing something wrong, or is there somethingfontmake
can do to makeotf
render as well asttf
?