[Bug 1009924] New: fonts look terrible after update to freetype 2.7
http://bugzilla.suse.com/show_bug.cgi?id=1009924 Bug ID: 1009924 Summary: fonts look terrible after update to freetype 2.7 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: bnc-team-screening@forge.provo.novell.com Reporter: jslaby@suse.com QA Contact: qa-bugs@suse.de CC: dimstar@opensuse.org, ismail@namtrac.org Found By: --- Blocker: --- CC: dimstar@opensuse.org, ismail@namtrac.org See the attachment (3 times magnified). Before the update, fonts were nice and readable. After the update, there is too much blur on the fonts and it looks pretty ugly. It happens both on tumbleweed and 42.2. In yast, I tried to set the default and autohinter profiles. It affected nothing. This has no effect too: FREETYPE_PROPERTIES=truetype:interpreter-version=35 dolphin I am not the only one experiencing it apparently: https://lists.opensuse.org/opensuse-factory/2016-10/msg00319.html -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1009924
http://bugzilla.suse.com/show_bug.cgi?id=1009924#c1
--- Comment #1 from Jiri Slaby
http://bugzilla.suse.com/show_bug.cgi?id=1009924
http://bugzilla.suse.com/show_bug.cgi?id=1009924#c2
--- Comment #2 from Jiri Slaby
http://bugzilla.suse.com/show_bug.cgi?id=1009924
http://bugzilla.suse.com/show_bug.cgi?id=1009924#c3
--- Comment #3 from Dominique Leuenberger
Created attachment 701757 [details] font screenshot
See the attachment (3 times magnified). Before the update, fonts were nice and readable. After the update, there is too much blur on the fonts and it looks pretty ugly. It happens both on tumbleweed and 42.2.
??? 42.2 was never updated to Freetype 2.7 - it ships with 2.6.3 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1009924
Chenzi Cao
http://bugzilla.suse.com/show_bug.cgi?id=1009924
http://bugzilla.suse.com/show_bug.cgi?id=1009924#c4
--- Comment #4 from Jiri Slaby
??? 42.2 was never updated to Freetype 2.7 - it ships with 2.6.3
Oh, right. I actually didn't check the version in 42.2. I updated from 13.2 to 42.2 on another machine and have the very same problem like with the recent tumbleweed update. So it wouldn't be directly connected to the freetype update, perhaps. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1009924
Jiri Slaby
http://bugzilla.suse.com/show_bug.cgi?id=1009924
Jiri Slaby
http://bugzilla.suse.com/show_bug.cgi?id=1009924
http://bugzilla.suse.com/show_bug.cgi?id=1009924#c5
Jiri Slaby
http://bugzilla.suse.com/show_bug.cgi?id=1009924
http://bugzilla.suse.com/show_bug.cgi?id=1009924#c6
--- Comment #6 from Jiri Slaby
http://bugzilla.suse.com/show_bug.cgi?id=1009924
http://bugzilla.suse.com/show_bug.cgi?id=1009924#c7
--- Comment #7 from Jiri Slaby
http://bugzilla.suse.com/show_bug.cgi?id=1009924
http://bugzilla.suse.com/show_bug.cgi?id=1009924#c8
Jiri Slaby
http://bugzilla.suse.com/show_bug.cgi?id=1009924
http://bugzilla.suse.com/show_bug.cgi?id=1009924#c9
Petr Gajdos
Petr, it could as well be a fontconfig configuration issue. I don't see 'font_type: "TT Instructed Font"(w)' in the noto fc-match output opposing to dejavu. Is is OK?
That is correct. The distinction between truetype instructed font and not truetype instructed font comes from /etc/fonts/conf.d/10-group-tt-non-hinted-fonts.conf originally from the infinality project. Fonts listed in that file will be rendered by freetype's truetype byte interpreter and that is why you see DejaVu rendered less blurred. Noto are not instructed at all as far as I know, so autohinter needs to be used (and I guess it is used despite the fontconfig is not saying it explicitly -- thats why it is 'force autohinting'). You can also try Liberation family of fonts if you like sharp rendering. You can achieve it quickly for example by 'Black and White profile' and clicking on 'font aliasing' afterwards if you want font aliasing (which is then not black and white anymore, obviously). Personally, I use bitmap font (Misc Fixed) for terminal (I am looking on it majority of time) because of nice black and white rendering. I have tried the subpixel rendering several times, but I do not like it too much because of color fringes (even on Windows). Also, make sure your desktop honors fontconfig setting. I know firefox should honor it for displaying pages, so I use it for testing. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1009924
http://bugzilla.suse.com/show_bug.cgi?id=1009924#c10
--- Comment #10 from Petr Gajdos
You can also try Liberation family of fonts if you like sharp rendering. You can achieve it quickly for example by 'Black and White profile' and clicking on 'font aliasing' afterwards if you want font aliasing (which is then not black and white anymore, obviously).
JFYI, and when you now click also on 'Force Autohinting On', you will see the difference between bytecode interpreter (sharp, but usable only with instructed fonts, fx. Liberation) and autohinter. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1009924
Vadim Krevs
http://bugzilla.suse.com/show_bug.cgi?id=1009924
Chenzi Cao
http://bugzilla.suse.com/show_bug.cgi?id=1009924
http://bugzilla.suse.com/show_bug.cgi?id=1009924#c11
Jiri Slaby
participants (1)
-
bugzilla_noreply@novell.com