So what is the consensus on if you have combining accents in a monospace typeface... should they be zero width, or does EVERY glyph need to be the mono width? #fontdev
So I've heard overlapping components in a hinted TT font is a big No — this comes up a lot in, for example, the `ç`, which usually has a `cedilla` component overlapping the `c` — but I've never seen an issue caused by overlapping components! But maybe I haven't been paying close enough attention.
Does anyone have an example of when overlapping components caused some sort of rendering issue?
Question, should the x/y min/max values found in a #VariableFont <head> table only match the min/max values of the default instance (i.e. the font whose outlines are in the <glyf> table), or should it reflect the min/max values of the whole variable font?
#fontdev question for everyone. Is the standard now to have the hhea values and the OS/2 values match?
I know it used to be common to have the OS/2 ascender value be the same as the value we but as the glyph dimension but this results in inconsistencies between mac and windows, right?
For some reason the Regular and Italic in the font I'm working on are in reversed order in Adobe apps... name tables are normal, pretty much the same as other fonts which are working, italic bits are set, all tests passing... any idea of other things to check?
Can anyone who’s familiar with Designspace 5.0 tell me how I can get an upright master and an italic (oblique) master to generate a single variable font? It seems using <axis-subset /> it’s an either/or situation.
Can someone please update me on CFF2? Is it… usable/stable? Can it be used realistically outside of Adobe apps? Any reason not to offer it to customers (alongside typical VF-TTFs of course)? Is it better to use AFDKO or FontMake for CFF2 fonts? Anything else I should know?
For some reason I’ve been sleeping on CFF2 fonts, would appreciate a schooling!
#font #engineering #fontdev #adobe #cff2 #variablefonts