On Thu, Dec 20, 2018 at 5:32 AM Werner LEMBERG wrote:
>
> > I just tested the static and variable fonts in macOS 10.14 TextEdit.
> > For the static instances, it presumably takes the hhea metrics, for
> > the VF, it always takes typo metrics. (It also adds the line gap at
> > the bottom, making
On Thu, Dec 20, 2018 at 6:02 AM Nikolaus Waxweiler
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
> 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
> I just tested the static and variable fonts in macOS 10.14 TextEdit.
> For the static instances, it presumably takes the hhea metrics, for
> the VF, it always takes typo metrics. (It also adds the line gap at
> the bottom, making text look weird, but maybe that's because the
> layout logic is
I just tested the static and variable fonts in macOS 10.14 TextEdit.
For the static instances, it presumably takes the hhea metrics, for
the VF, it always takes typo metrics. (It also adds the line gap at
the bottom, making text look weird, but maybe that's because the
layout logic is broken.)
So
OR MAYBEE if we detect a variable font, the default/static
outlines gets typo or win metrics instead of hhea metrics?
___
Freetype-devel mailing list
Freetype-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetype-devel
