Bug#730742: Font rendering fuzzy (straight lines smeared across subpixels) since upgrade to 2.5.1
Control: close -1 2.5.2-2 On Sat, Nov 01, 2014 at 10:48:09PM -0400, Michael Gilbert wrote: On Tue, Sep 23, 2014 at 12:45 PM, Steve Langasek wrote: So why not changing only the default UI font in GNOME until Cantarell gets fixed, instead of disabling a nice improvement like that? Droid or DejaVu could be a valid substitute in the meanwhile. I don't control what fonts the GNOME maintainers are using. You'll need to take this up with them with a bug report on the relevant packages. Since the core issue for this bug is gnome font choices, I don't think this belongs to freetype anymore. So, maybe it can be closed or reassigned to a gnome package? Yes, this bug should be closed; I hadn't realized it had been reopened. If there is a bug in the GNOME font, then as I said, someone should take that up with the maintainers via a bug report on the relevant packages. If and when those problems are fixed and we should re-evaluate the freetype defaults, someone can open a bug report against freetype again to ask for this change. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#730742: Font rendering fuzzy (straight lines smeared across subpixels) since upgrade to 2.5.1
On Tue, Sep 23, 2014 at 12:45 PM, Steve Langasek wrote: So why not changing only the default UI font in GNOME until Cantarell gets fixed, instead of disabling a nice improvement like that? Droid or DejaVu could be a valid substitute in the meanwhile. I don't control what fonts the GNOME maintainers are using. You'll need to take this up with them with a bug report on the relevant packages. Since the core issue for this bug is gnome font choices, I don't think this belongs to freetype anymore. So, maybe it can be closed or reassigned to a gnome package? Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#730742: Font rendering fuzzy (straight lines smeared across subpixels) since upgrade to 2.5.1
On Wed, Sep 24, 2014 at 2:49 PM, Theppitak Karoonboonyanan t...@debian.org wrote: So, the issue seems not to be on the font itself, but rather on the rasterizer and people's preferences. I still agree with Jason Pleau that Adobe rasterizer should be preferred. The reason I didn't ship OTF in my packages earlier was that, with the old rasterizer, while the glyphs appeared sharp for some sizes, they appeared inconsistent on some others. I've created a waterfall test page for Cantarell font here: http://linux.thai.net/~thep/tmp/fonttest/cantarell-waterfall.html The paragraphs start from 6pt, then increase by 1pt up to 16pt. And the results of the old rasterizer is: http://linux.thai.net/~thep/shots/20140924-cantarell-wf-old-engine.png Notice the inconsistent stem widths at 12pt and 13pt for regular weight, where the horizontal and diagonal stems appear thicker than vertical ones. (Look at the glyph M, O, Q, q, for example. And look how X appears thicker than F, T, H, E.) And notice how the glyphs get suddenly thicker from 13pt to 14pt. Now compare it with the result of Adobe rasterizer: http://linux.thai.net/~thep/shots/20140924-cantarell-wf-new-engine.png The stem widths are more consistent both within the same size and between different sizes. FYI, as the freeze is coming close, while my life has been extremely busy lately (I'm getting married), I'm reverting my font packages to TTF for now, although I think Adobe CFF rasterizer should be preferred in general, even for Cantarell itself, not just for my fonts. Regards, -- Theppitak Karoonboonyanan http://linux.thai.net/~thep/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#730742: Font rendering fuzzy (straight lines smeared across subpixels) since upgrade to 2.5.1
On Tue, Sep 23, 2014 at 1:47 PM, Steve Langasek vor...@debian.org wrote: So if this is only a problem with the GNOME3 default font, please get that font fixed in Debian, after which I am willing to reinstate the Adobe engine. But I'm not willing to enable it while it represents a regression vs. wheezy for a significant number of our desktop users. Here's my first try, using fontforge: - Apply autohint to all glyphs. - Adjust BlueValues to cover all glyphs to prevent overshoots on some glyphs without touching the splines. It appears to address a different problem: overshooting on small sizes, not the stem fuzziness as raised in this bug. So, the issue seems not to be on the font itself, but rather on the rasterizer and people's preferences. I still agree with Jason Pleau that Adobe rasterizer should be preferred. The reason I didn't ship OTF in my packages earlier was that, with the old rasterizer, while the glyphs appeared sharp for some sizes, they appeared inconsistent on some others. I've created a waterfall test page for Cantarell font here: http://linux.thai.net/~thep/tmp/fonttest/cantarell-waterfall.html The paragraphs start from 6pt, then increase by 1pt up to 16pt. And the results of the old rasterizer is: http://linux.thai.net/~thep/shots/20140924-cantarell-wf-old-engine.png Notice the inconsistent stem widths at 12pt and 13pt for regular weight, where the horizontal and diagonal stems appear thicker than vertical ones. (Look at the glyph M, O, Q, q, for example. And look how X appears thicker than F, T, H, E.) And notice how the glyphs get suddenly thicker from 13pt to 14pt. Now compare it with the result of Adobe rasterizer: http://linux.thai.net/~thep/shots/20140924-cantarell-wf-new-engine.png The stem widths are more consistent both within the same size and between different sizes. Regards, -- Theppitak Karoonboonyanan http://linux.thai.net/~thep/ Cantarell-Regular.otf Description: application/vnd.oasis.opendocument.formula-template
Bug#730742: Font rendering fuzzy (straight lines smeared across subpixels) since upgrade to 2.5.1
On Tue, Sep 23, 2014 at 09:25:33AM +0700, Theppitak Karoonboonyanan wrote: Package: libfreetype6 Version: 2.5.2-2 Followup-For: Bug #730742 Control: reopen -1 Dear Maintainer, I also prefer Adobe rasterizer, to the point that my font packages, namely fonts-tlwg-*, have switched from TTF to OTF due to the improved quality it provides. The result was better control on glyph shapes (because the fonts are developed using cubic splines) with smaller installation size. Switching back to the old engine causes regression on my fonts, especially on terminal with dark background: New engine: http://linux.thai.net/~thep/shots/20140923-tlwgtypo-new-engine-2.png Old engine: http://linux.thai.net/~thep/shots/20140923-tlwgtypo-old-engine-2.png New engine: http://linux.thai.net/~thep/shots/20140923-tlwgtypo-new-engine-1.png Old engine: http://linux.thai.net/~thep/shots/20140923-tlwgtypo-old-engine-1.png So, I agree with Jason Pleau that Adobe engine is preferred. However, instead of providing alternative packages, I think the patch should be reverted and the poorly-hinted Cantarell font be fixed instead, as pointed out here in upstream mailing list (according to BubuXP's comment #118 above): https://lists.nongnu.org/archive/html/freetype/2014-01/msg00011.html I've checked Cantarell font, and its hints are really poor as described. I'm reopening the bug, so the discussion can be continued. So if this is only a problem with the GNOME3 default font, please get that font fixed in Debian, after which I am willing to reinstate the Adobe engine. But I'm not willing to enable it while it represents a regression vs. wheezy for a significant number of our desktop users. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Bug#730742: Font rendering fuzzy (straight lines smeared across subpixels) since upgrade to 2.5.1
Il 23/set/2014 08:51 Steve Langasek vor...@debian.org ha scritto: So if this is only a problem with the GNOME3 default font, please get that font fixed in Debian, after which I am willing to reinstate the Adobe engine. But I'm not willing to enable it while it represents a regression vs. wheezy for a significant number of our desktop users. So why not changing only the default UI font in GNOME until Cantarell gets fixed, instead of disabling a nice improvement like that? Droid or DejaVu could be a valid substitute in the meanwhile.
Bug#730742: Font rendering fuzzy (straight lines smeared across subpixels) since upgrade to 2.5.1
On Tue, Sep 23, 2014 at 10:47:11AM +0200, BubuXP wrote: Il 23/set/2014 08:51 Steve Langasek vor...@debian.org ha scritto: So if this is only a problem with the GNOME3 default font, please get that font fixed in Debian, after which I am willing to reinstate the Adobe engine. But I'm not willing to enable it while it represents a regression vs. wheezy for a significant number of our desktop users. So why not changing only the default UI font in GNOME until Cantarell gets fixed, instead of disabling a nice improvement like that? Droid or DejaVu could be a valid substitute in the meanwhile. I don't control what fonts the GNOME maintainers are using. You'll need to take this up with them with a bug report on the relevant packages. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Bug#730742: Font rendering fuzzy (straight lines smeared across subpixels) since upgrade to 2.5.1
Package: libfreetype6 Version: 2.5.2-2 Followup-For: Bug #730742 Control: reopen -1 Dear Maintainer, I also prefer Adobe rasterizer, to the point that my font packages, namely fonts-tlwg-*, have switched from TTF to OTF due to the improved quality it provides. The result was better control on glyph shapes (because the fonts are developed using cubic splines) with smaller installation size. Switching back to the old engine causes regression on my fonts, especially on terminal with dark background: New engine: http://linux.thai.net/~thep/shots/20140923-tlwgtypo-new-engine-2.png Old engine: http://linux.thai.net/~thep/shots/20140923-tlwgtypo-old-engine-2.png New engine: http://linux.thai.net/~thep/shots/20140923-tlwgtypo-new-engine-1.png Old engine: http://linux.thai.net/~thep/shots/20140923-tlwgtypo-old-engine-1.png So, I agree with Jason Pleau that Adobe engine is preferred. However, instead of providing alternative packages, I think the patch should be reverted and the poorly-hinted Cantarell font be fixed instead, as pointed out here in upstream mailing list (according to BubuXP's comment #118 above): https://lists.nongnu.org/archive/html/freetype/2014-01/msg00011.html I've checked Cantarell font, and its hints are really poor as described. I'm reopening the bug, so the discussion can be continued. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores) Locale: LANG=th_TH.UTF-8, LC_CTYPE=th_TH.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libfreetype6 depends on: ii libc6 2.19-11 ii libpng12-0 1.2.50-2 ii multiarch-support 2.19-11 ii zlib1g 1:1.2.8.dfsg-2 libfreetype6 recommends no packages. libfreetype6 suggests no packages. -- no debconf information -- Theppitak Karoonboonyanan http://linux.thai.net/~thep/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#730742: Font rendering fuzzy (straight lines smeared across subpixels) since upgrade to 2.5.1
I can see that this patch fixed the issue for some people, I (and maybe others too?) preferred the way the fonts were rendered with the Adobe hinter. From what I can see we can't have both in the same package as the engine used (freetype or adobe) is decided at compile time. Is there something we can do to allow both versions to be in Debian? Perhaps another package with the Adobe engine enabled, that would conflict with libfreetype6 ? Jason -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#730742: Font rendering fuzzy (straight lines smeared across subpixels) since upgrade to 2.5.1
Package: libfreetype6 Followup-For: Bug #730742 Following up again: any chance of addressing this regression in the next version of the Debian package, such as by applying the patch to disable the Adobe hinter? I'd like to make sure this issue gets fixed before the next stable release. - Josh Triplett -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#730742: Font rendering fuzzy (straight lines smeared across subpixels) since upgrade to 2.5.1
Package: libfreetype6 Followup-For: Bug #730742 Any status update on this issue? I still have libfreetype6 on hold on all my systems, and it sounds like many others observe this issue as well. - Josh Triplett -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#730742: Font rendering fuzzy (straight lines smeared across subpixels) since upgrade to 2.5.1
This same bug has been reported in FreeType mailing list: http://lists.nongnu.org/archive/html/freetype/2014-01/msg6.html Here are the results: http://lists.nongnu.org/archive/html/freetype/2014-01/msg00011.html Adobe engine is ok, the bug is located in: - the rendering engine expect gamma correction to be used in the system (suggested value of 1.8), but it isn't (value is 1.0); - some incorrect Cantarell's hint instructions. Somebody knows where to set the gamma correction? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#730742: Font rendering fuzzy (straight lines smeared across subpixels) since upgrade to 2.5.1
It looks like I spoke too soon. With the new version of libfreetype6 (2.5.1-1) and the fontconfig configuration above, most font rendering matches the behavior of 2.4.9-1.1, but some things still render differently. For instance, see the attached screenshots of gnome-terminal. The terminal contents seem to render identically, but the tab labels get blurry with 2.5.1-1, even with the configuration from above. I cannot find any screenshot... I suspect that Gnome overwrites the hinting settings of ~/.config/fontconfig/fonts.conf I know that Gnome3 sets Xft values that override fontconfig settings, but I don't know if it's the case. To check the Xft values, type xrdb -query. Try changing the hintstyle setting from gnome-tweak-tool and watch if Cantarell font changes concordantly. It should not change, because mode=assign has been used in the patch above. But if it changes, then that means Gnome overrides the fontconfig fonts settings of the patch (bug?). At this point you should set slight hinting in gnome-tweak-tool to see if Cantarell looks good. Version 2.5.2-1 has been released, you could also try if something changes with this version. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#730742: Font rendering fuzzy (straight lines smeared across subpixels) since upgrade to 2.5.1
On Sat, Dec 21, 2013 at 11:23:57AM -0800, Josh Triplett wrote: On Mon, Dec 16, 2013 at 11:53:01AM +0100, BubuXP wrote: I found the cause (maybe). Probably the fuzzy fonts are all OpenType fonts. Starting from freetype 2.5.0.1, the Adobe CFF engine is the default rasterizer for those class of fonts. https://blogs.adobe.com/typblography/2013/05/adobe-contributes-cff-rasterizer-to-freetype.html From: http://lists.freedesktop.org/archives/fontconfig/2013-December/005026.html If I remember correctly the new Adobe CFF hinter hinting levels are out of sync with the autohinter used with TTF fonts. As reported in the above link, to mitigate the bug this fix should be enabled by default in the next fontconfig version (2.11.1, that will be released soon): match target=font test name=fontformat compare=eq stringCFF/string /test edit name=hintstyle mode=assign consthintslight/const /edit /match I can confirm that adding that to ~/.config/fontconfig/fonts.conf (with the appropriate XML wrapping for a fontconfig config file) solves the problem. I took screenshots of the same dialog with 2.4.9-1.1 and with 2.5.1-1 using the above config snippet, and got binary-identical screenshot PNGs. On Mon, Dec 16, 2013 at 09:50:33AM -0800, Steve Langasek wrote: Use of the Adobe hinter is optional and the default can be changed at compile time. Does someone who's hitting this bug want to try rebuilding freetype locally with the option changed, to see if that fixes it? (If not, I'll prepare a test build for people to try, but it'll take a few days before I can get to it.) I'd actually recommend *against* disabling the new hinter. I've seen several examples of hinted fonts displaying better with the new hinter. I'd simply recommend fixing the hintstyle mechanism such that it respects the same configuration as the previous hinter, so that anyone using slight hinting with the previous hinter will continue to get slight hinting with the new hinter. It looks like I spoke too soon. With the new version of libfreetype6 (2.5.1-1) and the fontconfig configuration above, most font rendering matches the behavior of 2.4.9-1.1, but some things still render differently. For instance, see the attached screenshots of gnome-terminal. The terminal contents seem to render identically, but the tab labels get blurry with 2.5.1-1, even with the configuration from above. - Josh Triplett -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#730742: Font rendering fuzzy (straight lines smeared across subpixels) since upgrade to 2.5.1
On Mon, Dec 16, 2013 at 11:53:01AM +0100, BubuXP wrote: I found the cause (maybe). Probably the fuzzy fonts are all OpenType fonts. Starting from freetype 2.5.0.1, the Adobe CFF engine is the default rasterizer for those class of fonts. https://blogs.adobe.com/typblography/2013/05/adobe-contributes-cff-rasterizer-to-freetype.html From: http://lists.freedesktop.org/archives/fontconfig/2013-December/005026.html If I remember correctly the new Adobe CFF hinter hinting levels are out of sync with the autohinter used with TTF fonts. As reported in the above link, to mitigate the bug this fix should be enabled by default in the next fontconfig version (2.11.1, that will be released soon): match target=font test name=fontformat compare=eq stringCFF/string /test edit name=hintstyle mode=assign consthintslight/const /edit /match I can confirm that adding that to ~/.config/fontconfig/fonts.conf (with the appropriate XML wrapping for a fontconfig config file) solves the problem. I took screenshots of the same dialog with 2.4.9-1.1 and with 2.5.1-1 using the above config snippet, and got binary-identical screenshot PNGs. On Mon, Dec 16, 2013 at 09:50:33AM -0800, Steve Langasek wrote: Use of the Adobe hinter is optional and the default can be changed at compile time. Does someone who's hitting this bug want to try rebuilding freetype locally with the option changed, to see if that fixes it? (If not, I'll prepare a test build for people to try, but it'll take a few days before I can get to it.) I'd actually recommend *against* disabling the new hinter. I've seen several examples of hinted fonts displaying better with the new hinter. I'd simply recommend fixing the hintstyle mechanism such that it respects the same configuration as the previous hinter, so that anyone using slight hinting with the previous hinter will continue to get slight hinting with the new hinter. - Josh Triplett -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#730742: Font rendering fuzzy (straight lines smeared across subpixels) since upgrade to 2.5.1
I found the cause (maybe). Probably the fuzzy fonts are all OpenType fonts. Starting from freetype 2.5.0.1, the Adobe CFF engine is the default rasterizer for those class of fonts. https://blogs.adobe.com/typblography/2013/05/adobe-contributes-cff-rasterizer-to-freetype.html From: http://lists.freedesktop.org/archives/fontconfig/2013-December/005026.html If I remember correctly the new Adobe CFF hinter hinting levels are out of sync with the autohinter used with TTF fonts. As reported in the above link, to mitigate the bug this fix should be enabled by default in the next fontconfig version (2.11.1, that will be released soon): match target=font test name=fontformat compare=eq stringCFF/string /test edit name=hintstyle mode=assign consthintslight/const /edit /match -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#730742: Font rendering fuzzy (straight lines smeared across subpixels) since upgrade to 2.5.1
On Mon, Dec 16, 2013 at 11:53:01AM +0100, BubuXP wrote: I found the cause (maybe). Probably the fuzzy fonts are all OpenType fonts. Starting from freetype 2.5.0.1, the Adobe CFF engine is the default rasterizer for those class of fonts. https://blogs.adobe.com/typblography/2013/05/adobe-contributes-cff-rasterizer-to-freetype.html Yes, this is the change that I suspected would be the source of the problem. I just haven't had time yet to set up an environment where I could reproduce it to confirm. Use of the Adobe hinter is optional and the default can be changed at compile time. Does someone who's hitting this bug want to try rebuilding freetype locally with the option changed, to see if that fixes it? (If not, I'll prepare a test build for people to try, but it'll take a few days before I can get to it.) From: http://lists.freedesktop.org/archives/fontconfig/2013-December/005026.html If I remember correctly the new Adobe CFF hinter hinting levels are out of sync with the autohinter used with TTF fonts. As reported in the above link, to mitigate the bug this fix should be enabled by default in the next fontconfig version (2.11.1, that will be released soon): match target=font test name=fontformat compare=eq stringCFF/string /test edit name=hintstyle mode=assign consthintslight/const /edit /match -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#730742: Font rendering fuzzy (straight lines smeared across subpixels) since upgrade to 2.5.1
On Thu, 12 Dec 2013 13:10:01 -0800, Steve Langasek wrote: This is not garbage display. I was sure this was the problem but seems I was wrong, sorry. Probably I will be wrong this time too, but if possible I'd like to know by those affected by the bug: - the desktop environment they are using and its fonts settings; - their fontconfig configuration (conf.d/, local.conf, .fonts.conf); - the output of xrdb -query. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#730742: Font rendering fuzzy (straight lines smeared across subpixels) since upgrade to 2.5.1
Version 2.5.2 has been released meantime, where probably the problem has been fixed: CHANGES BETWEEN 2.5.1 and 2.5.2 I. IMPORTANT BUG FIXES - Improving the display of some broken TrueType fonts introduced a bug that made FreeType crash on some popular (but not fully conformant) fonts like `ahronbd.ttf'. - Another round of improvements to correct positioning and hinting of composite glyphs in TrueType fonts. II. MISCELLANEOUS - Version 2.5.1 introduced a bug in handling embedded bitmap strikes of TrueType fonts, causing garbage display under some circumstances. - The `ftgrid' demo programcouldn't be compiled in non-development builds. Two other patches released after 2.5.2 to fix this problem: http://lists.nongnu.org/archive/html/freetype-devel/2013-12/msg00013.html could further improve some fonts aspect. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#730742: Font rendering fuzzy (straight lines smeared across subpixels) since upgrade to 2.5.1
On Thu, Dec 12, 2013 at 09:55:22PM +0100, BubuXP wrote: Version 2.5.2 has been released meantime, where probably the problem has been fixed: Which of these changes are you claiming fixes the issue? CHANGES BETWEEN 2.5.1 and 2.5.2 I. IMPORTANT BUG FIXES - Improving the display of some broken TrueType fonts introduced a bug that made FreeType crash on some popular (but not fully conformant) fonts like `ahronbd.ttf'. We're not talking about a crash, this is not relevant. - Another round of improvements to correct positioning and hinting of composite glyphs in TrueType fonts. This bug is not about composite glyphs. II. MISCELLANEOUS - Version 2.5.1 introduced a bug in handling embedded bitmap strikes of TrueType fonts, causing garbage display under some circumstances. This is not garbage display. - The `ftgrid' demo programcouldn't be compiled in non-development builds. Nothing to do with ftgrid. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Bug#730742: Font rendering fuzzy (straight lines smeared across subpixels) since upgrade to 2.5.1
FYI, I tried dpkg-reconfigure fontconfig-config and switching to Autohinter, which made the letters look a bit thinner, but the look improved overall (YMMV). -- Jindřich Makovička -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#730742: Font rendering fuzzy (straight lines smeared across subpixels) since upgrade to 2.5.1
Am Donnerstag, den 05.12.2013, 08:37 -0800 schrieb Steve Langasek: If you want to disable the *use* of subpixel rendering, I believe there's a fontconfig option for this. But we should not disable the *capability* for subpixel rendering in freetype. I wonder why the capability is not enabled by default upstream but needs a patch in Debian? - Fabian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#730742: Font rendering fuzzy (straight lines smeared across subpixels) since upgrade to 2.5.1
On Thu, Dec 05, 2013 at 01:13:08PM -0800, Josh Triplett wrote: On Thu, Dec 05, 2013 at 08:37:59AM -0800, Steve Langasek wrote: On Thu, Dec 05, 2013 at 09:23:56AM +0100, Fabian Greffrath wrote: Confirmed with the upstream version, but only when FT_CONFIG_OPTION_SUBPIXEL_RENDERING is enabled, which is the case in the Debian build but not in the default upstream build. please disable enable-subpixel-rendering.patch in the next upload of the freetype package. No. Subpixel rendering is an important improvement for preserving the shape of small fonts on LCD displays. The fact that some fonts are currently rendered poorly with it (which so far I haven't been able to reproduce with the fonts I'm using) does not warrant disabling this functionality altogether. If you want to disable the *use* of subpixel rendering, I believe there's a fontconfig option for this. But we should not disable the *capability* for subpixel rendering in freetype. Agreed, I definitely don't think subpixel rendering should be turned off entirely, or even turned off by default; this is a regression introduced in the new version of freetype. See the screenshots I posted; *both* of them have obvious subpixel rendering, but the previous freetype does sensible hinting that respects pixel boundaries and the current one does not. I use the default GNOME 3 fonts across the board (Cantarell and DejaVu), modulo font sizes. Maybe to make it more clear what Josh says: If you upgrade freetype from 2.4.9-1.1 to 2.5.1-1 on a system with perfectly looking fonts, your fonts look ugly afterwards. I noticed that the font hinting levels are affected. If I choose slight hinting, all fonts except the monospace one in the terminal look OK again (the terminal looks ugly then, but looked OK before). And there is no difference between medium and full hinting in 2.5.1. Subpixel hinting on or off does not make any difference. This is very annoying. -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. Please do not top-post if possible. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#730742: Font rendering fuzzy (straight lines smeared across subpixels) since upgrade to 2.5.1
Dear Steve, Confirmed with the upstream version, but only when FT_CONFIG_OPTION_SUBPIXEL_RENDERING is enabled, which is the case in the Debian build but not in the default upstream build. please disable enable-subpixel-rendering.patch in the next upload of the freetype package. - Fabian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#730742: Font rendering fuzzy (straight lines smeared across subpixels) since upgrade to 2.5.1
On Thu, Dec 05, 2013 at 09:23:56AM +0100, Fabian Greffrath wrote: Dear Steve, Confirmed with the upstream version, but only when FT_CONFIG_OPTION_SUBPIXEL_RENDERING is enabled, which is the case in the Debian build but not in the default upstream build. please disable enable-subpixel-rendering.patch in the next upload of the freetype package. No. Subpixel rendering is an important improvement for preserving the shape of small fonts on LCD displays. The fact that some fonts are currently rendered poorly with it (which so far I haven't been able to reproduce with the fonts I'm using) does not warrant disabling this functionality altogether. If you want to disable the *use* of subpixel rendering, I believe there's a fontconfig option for this. But we should not disable the *capability* for subpixel rendering in freetype. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Bug#730742: Font rendering fuzzy (straight lines smeared across subpixels) since upgrade to 2.5.1
On Thu, Dec 05, 2013 at 08:37:59AM -0800, Steve Langasek wrote: On Thu, Dec 05, 2013 at 09:23:56AM +0100, Fabian Greffrath wrote: Confirmed with the upstream version, but only when FT_CONFIG_OPTION_SUBPIXEL_RENDERING is enabled, which is the case in the Debian build but not in the default upstream build. please disable enable-subpixel-rendering.patch in the next upload of the freetype package. No. Subpixel rendering is an important improvement for preserving the shape of small fonts on LCD displays. The fact that some fonts are currently rendered poorly with it (which so far I haven't been able to reproduce with the fonts I'm using) does not warrant disabling this functionality altogether. If you want to disable the *use* of subpixel rendering, I believe there's a fontconfig option for this. But we should not disable the *capability* for subpixel rendering in freetype. Agreed, I definitely don't think subpixel rendering should be turned off entirely, or even turned off by default; this is a regression introduced in the new version of freetype. See the screenshots I posted; *both* of them have obvious subpixel rendering, but the previous freetype does sensible hinting that respects pixel boundaries and the current one does not. I use the default GNOME 3 fonts across the board (Cantarell and DejaVu), modulo font sizes. - Josh Triplett -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#730742: Font rendering fuzzy (straight lines smeared across subpixels) since upgrade to 2.5.1
Confirmed with the upstream version, but only when FT_CONFIG_OPTION_SUBPIXEL_RENDERING is enabled, which is the case in the Debian build but not in the default upstream build. -- Juliusz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#730742: Font rendering fuzzy (straight lines smeared across subpixels) since upgrade to 2.5.1
Package: libfreetype6 Version: 2.5.1-1 Followup-For: Bug #730742 I can confirm this too, though some fonts still render fine. For example, Cantarell (default GNOME3 font) renders fuzzy, but BitStream Vera Sans renders fine. Regards, Colomban -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
