You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CFF2 has a file size advantage over TrueType-flavored variable fonts, specially if one doesn't care about hinting (mobile, retina display, etc) but does care about (uncompressed) size.
CFF2 also alleviates some other limitations of variable-fonts built against the gvar table. Unfortunately, it imposes its own limitations. These are among the issues I'm going to raise.
Ideally, Adobe folks choose to turn these ideas into proposals and push it through the OFF standardization / OpenType integration process. Failing that, we might want to go ahead and do it. cc @davelab6
I'll try to get some discussion started on these things within Adobe. There's a lot of history here, of course, so it might take some time to dig up why things are as they are.
I'll try to get some discussion started on these things within Adobe. There's a lot of history here, of course, so it might take some time to dig up why things are as they are.
CFF2 has a file size advantage over TrueType-flavored variable fonts, specially if one doesn't care about hinting (mobile, retina display, etc) but does care about (uncompressed) size.
CFF2
also alleviates some other limitations of variable-fonts built against thegvar
table. Unfortunately, it imposes its own limitations. These are among the issues I'm going to raise.Ideally, Adobe folks choose to turn these ideas into proposals and push it through the OFF standardization / OpenType integration process. Failing that, we might want to go ahead and do it. cc @davelab6
CFF2
] DeprecateFontMatrix
#156CFF2
] Conflicting text regarding the default vsindex when processing CharStrings #157CFF2
] Allow more than onevsindex
operation and at any place #158CFF2
]uint16 VariationStore.length
limitation #159The text was updated successfully, but these errors were encountered: