Re: [ft] FREETYPE_PROPERTIES alternative?

[Volth]

I see that it is not relevant to "35" because I have the problem with
2.7.1 irregardless of "35" or "40", but there is no problem with
2.6.5.
Fonts and fontconfig's xmls are the same.
I will try to bisect which commit caused this regression.

On 4/19/17, Werner LEMBERG <address@hidden> wrote:
>
>> You are right, no configurable setting could fix fonts in Chrome, only
>> downgrade to 2.6.5.
>
> Mhmm, you should have some success probably with current git of
> FreeType – there was a bug, as mentioned in the report.  Maybe current
> Chrome git versions allow `FREETYPE_PROPERTIES'...
>
>> I tried to  hardcode "truetype:interpreter-version=35"
>> The fonts in Chrome looks: http://i.imgur.com/g9q9y2I.png
>> Note the bold font in names.
>
> There must be something else going on.  What I see in this image is
> B/W rendering of the fonts!  This is *not* related to interpreter
> version 35, which of course supports anti-aliasing.
>
> Note that only a very small set of fonts available today have good
> enough B/W hinting.
>
>
>     Werner
>