|
From: | Nikolaus Waxweiler |
Subject: | Re: [ft-devel] Taming CFF_CONFIG_OPTION_DARKENING_PARAMETER_Y* for a gamma of ~2.2/sRGB? |
Date: | Sat, 8 Aug 2015 09:17:31 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 |
(Repost because I forgot to click "post to list", sorry Werner..)
Indeed. So why doesn't get this applied? Is there a negative impact somewhere? Perhaps you should add the patch to the bug report; maybe this helps move the dinosaurs...
The author noted that "CAIRO_DEBUG=xrender-version=-1" triggers software rendering, so I personally only rigged firefox.desktop and thunderbird.desktop to load it and leave the rest of the desktop hardware-accelerated ;) This patch will probably need to touch other parts of the stack, but I will bug some cairo (and skia/QT?) people to see if there's something that can be done to bring Linux font rendering into the 21st century ;)
Side note 1: Firefox on Windows (with DirectWrite enabled for all fonts) does gamma correction for fonts, as does Edge. So it would be bringing the Linux version up to parity.
Side note 2: For years I didn't like the autohinter, I always thought it's output looked... pixely, blotchy, color-fringy... the opposite of nice, depending on the size. Wasted a lot of time fiddling with Infinality's patches, stem darkening, etc. It's a bit embarrassing that the problem has been gamma correction the entire time and that the autohinter is doing perfectly fine, even if the output is a bit thin. Which brings us to stem darkening again ;)
[Prev in Thread] | Current Thread | [Next in Thread] |