On Thu, Dec 20, 2018 at 6:02 AM Nikolaus Waxweiler <[email protected]> wrote:
> > This is certainly the most convenient solution for me since I have > > nothing to do on the FreeType side :-) > > (As an aside, GTK/Pango seem to make the same mistake as TextEdit then, > putting the line gap at the bottom instead of on both sides or something, > so this would still look wrong even if FT would default to typo metrics for > VFs) > lineGap should be put in between two neighboring lines only. > > Your question, however, is a fundamental one: Shall a VF font be > > always treated as VF, or is the `VFness' an optional feature? > > I'd say the primary purpose of a VF is to be a VF, it is only optionally > so for applications that don't know what a VF is. You'd think that using > the hhea metrics for the default outlines would make sense in that case, > but this still presents a corner case if the applications increases in > smartness and suddenly the same font has different metrics 🤔 > -- behdad http://behdad.org/
_______________________________________________ Freetype-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/freetype-devel
