> Also, I don't think it's necessarily too late to get the information
> after FT_Load_Glyph is called.
Adam, Ben,
To be honest, I do not quite follow how Chromium does text rendering.
It was under impression that you guys do font atlasing (aka preloading
of font texture). We just provided
On Mon, Feb 19, 2018 at 3:05 PM, Werner LEMBERG wrote:
> What I need is a reliable mechanism (across Freetype versions and
> fonts) to determine if a font has horizontal hinting applied or
> not. It looks like it's something Freetype might need to
> provide, since
What I need is a reliable mechanism (across Freetype versions and
fonts) to determine if a font has horizontal hinting applied or
not. It looks like it's something Freetype might need to
provide, since the true answer seems to come from the interaction
of flags, fonts,
On Tue, Feb 13, 2018 at 4:39 AM, Chris Liddell
wrote:
> Using C99 types, with sane fallbacks makes sense, but using the more
> invasive parts of C99 (like mixing declarations and code) could be
> problematic.
This is basically what FreeType is doing already. FreeType
On Mon, Feb 12, 2018 at 4:39 PM, Werner LEMBERG wrote:
>> Can we properly use the FT_List data field as an actual pointer to
>> the glyph index instead of stuffing the integer into the pointer?
>
> Certainly, if you are going to dynamically allocate a slot for it.
> I tried to avoid
On Mon, Feb 19, 2018 at 6:41 AM, Alexei Podtelezhnikov
wrote:
> On Sun, Feb 18, 2018 at 6:11 PM, Werner LEMBERG wrote:
>>> What I need is a reliable mechanism (across Freetype versions and
>>> fonts) to determine if a font has horizontal hinting applied or not.
On Sun, Feb 18, 2018 at 6:11 PM, Werner LEMBERG wrote:
>> What I need is a reliable mechanism (across Freetype versions and
>> fonts) to determine if a font has horizontal hinting applied or not.
>> It looks like it's something Freetype might need to provide, since
>> the true