On 18.07.2017, Andreas M. Kirchwitz wrote: > Do you know why the font display looks broken with the new v40 engine? > Is that a bug in the freetype library or something that has to be > fixed in all applications? It's not a bug, it's meant to be a feature :-( https://tinyurl.com/ybf3fkwv > Starting with F26, Chrome now respects the anti-aliasing config, > but although I have have turned Hinting on (which is essential for > nice font rendering, even with AA turned off), Chrome displays those > fonts without Hinting. That looks horrible. :-( I've never used Chrome, so I don't know what's going on there. You could do a diff between the latest Chrome that worked and the new one, just to see if there's something that rings a bell. > > If you also want subpixel rendering, which now is disabled by default, > > you can dig into the foption.h file in the config directory of the > > freetype sourcecode, uncomment the option and recompile. > Does that mean, subpixel rendering has been completely removed > from the freetype library compiled for F26? Any reason for this? Seems to be the case. Looking into the latest 2.7.1 source shipped by Fedora, subpixel rendering isn't enabled in foptions.h. Most probably, Fedora follows the freetype principal developers opinion(s). > Subpixel rendering has no effect if AA is turned off, right? As far as I understand it, subpixel rendering is a form of antialiasing on LCD screens that works because the combination of red, green and blue appears as white light. A typical example is Micro$ofts "Cleartype". To me, v40 is far superior to v35. Fortunately, there's a way to switch back to v35 behaviour. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
