Issue metadata
Sign in to add a comment
|
Linux subpixel rendering looks worse with FreeType v40 hinter than with v35 |
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3198.0 Safari/537.36 Steps to reproduce the problem: 1. Open gmail in chrome versions 60, 61, or 62 in Gnome 3 (or possibly other linux window managers). 2. Observe blurry fonts. What is the expected behavior? Non-blurry fonts as in versions 59 and prior. What went wrong? Probably related to issue 726631 . As with that issue, setting the environment variable `export FREETYPE_PROPERTIES="truetype:interpreter-version=35"` fixes (or at least works around) the problem. I tried this on the current stable (60) beta (61) and dev (62) versions with the same behavior in each. I also tried all of the values for chrome://flags/#enable-gpu-rasterization using v62. None of theme seemed to make a difference. Attached are two screenshots of the 'good' and 'bad' states from v62. Did this work before? Yes 59 Chrome version: 62.0.3198.0 Channel: dev OS Version: Flash Version:
,
Aug 30 2017
(and if anyone remembers how to mark bugs not RVG, please do so :-P)
,
Aug 30 2017
,
Aug 30 2017
It appears (based on FREETYPE_PROPERTIES="truetype:interpreter-version=35" restoring the old rendering style) that this is due to the FreeType v40 hinter rather than anything on Chrome's side. As described in issue 726631 , Chrome bundles its own up-to-date copy of FreeType now, but once distros eventually ship their own updated copies of FreeType, other apps will likely exhibit the same text rendering. Ben, is that correct? Do you happen to know if any work is being done upstream to improve antialiased output from the v40 hinter? I see a couple of possibly-relevant reports, e.g. http://savannah.nongnu.org/bugs/?func=detailitem&item_id=51051 and http://savannah.nongnu.org/bugs/?func=detailitem&item_id=51387, but I think they mostly resolve around non-AA rendering, which I believe you've fixed.
,
Aug 31 2017
The bug is in the eye of the beholder. v40 tuns off horizontal hinting (as in Vista) the glyph shapes are better and the spacing is improved. It is different, but it is not bad. https://www.freetype.org/freetype2/docs/subpixel-hinting.html
,
Sep 22 2017
,
Sep 22 2017
I can't really agree with "different but not bad". I personally find the new text to cause significantly more eyestrain to the point where I can't really use the browser with the new font hinting.
,
Sep 22 2017
I should clarify: my issue is specifically with the bluriness. Other aspects like spacing are fine.
,
Sep 26 2017
You software and hardware gamma settings may be worse than for most people. Seriously, it matters. Chromium browser is actually the best browser to deal with this, unless your monitor is completely off-base (gamma should be near 1.8). Check out this page and see if those striped glyphs hurt your eyes; they should not. https://www.freetype.org/freetype2/docs/rasterinfo/rasterinfo.html
,
Sep 13
Archiving old bugs that haven't been actively assigned in over 180 days. If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!
,
Sep 13
Archiving old bugs that haven't been actively assigned in over 180 days. If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!
,
Sep 13
Archiving old bugs that haven't been actively assigned in over 180 days. If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!
,
Sep 14
I just confirmed that this is still an issue for me with Chromium distributed with Debian (currently 69.0.3497.81). There is still a significant (and in my opinion worse) difference with the default configuration. Using FREETYPE_PROPERTIES="truetype:interpreter-version=35" gets rid of most of the blurriness. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by thakis@chromium.org
, Aug 30 2017Status: Untriaged (was: Unconfirmed)