| Summary: | x11-libs/cairo 1.10.0 causes font rendering regression with subpixel smoothing | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Mark R. Pariente <markpariente> |
| Component: | [OLD] Library | Assignee: | Gentoo X packagers <x11> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | arne.flagge, bugzilla-gentoo, cardoe, ghepeu, hans, marduk, peter, rafdev, rahul, spatz |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Mark R. Pariente
2010-09-09 06:41:48 UTC
I was expecting this behaviour with the removal of the "lcdfilter" and the "cleartype" flags. What I would like to know whether these patches have been merged upstream or are we waiting for a compatible release? Also ran into this, the ChangeLog doesn't say why these USE flags were removed, and looking at the 1.9.10 upstream changelog I found: Also to the relief of many we have included the downstream patch to honour the user's LCD filtering preferences for subpixel rendering of fonts. The interface remains private for the time being, whilst the proposed public API is finalized. So not sure if this means the patch isn't needed anymore and wether it's supposed to just work now and maybe something else is wrong I guess it is still needed, there is a supposedly working patch in bug #331743 Perhaps the situation w.r.t. this can be made clearer via an elog/ewarn message or an eselect news message? This patch in that bug report is useless, it just duplicates in cairo the functionality provided by freetype. To enable cleartype-like filtering again you need the fontconfig patch you can find in bug 306053 and then you have to run eselect fontconfig enable 11-lcdfilter-default.conf (In reply to comment #5) > This patch in that bug report is useless, it just duplicates in cairo the > functionality provided by freetype. > > To enable cleartype-like filtering again you need the fontconfig patch you can > find in bug 306053 and then you have to run > > eselect fontconfig enable 11-lcdfilter-default.conf What does this mean? I just emerged cairo 1.10.2-r1 which just went stable, and after noticing my eyes were hurting from trying to read these all too colorful I’s and i’s and any vertical bar-like character, I ended up reverting to cairo 1.8.10 . So I read here that the patch activated by the cleartype USE flag has been integrated upstream, and it’s to be enabled via fontconfig, so in turn via eselect-fontconfig. Too bad the configuration replacing the patch still isn’t there. For me, I can easily add the missing files myself. But what about other users, especially newcomers? Do they really have to struggle with imperfect hinting, before understanding what’s wrong and still not be able to apply the solution? Is there a reason cairo 1.10 went stable removing something that was supposed to be added back by a version/revision of fontconfig which just doesn’t exist yet? This is not a bug in cairo. Just use your freetype correctly (this probably should be documented properly, but nothing x11/cairo maintainers should do). (In reply to comment #7) > This is not a bug in cairo. > > Just use your freetype correctly (this probably should be documented properly, > but nothing x11/cairo maintainers should do). What does this mean? How do I “use my freetype correctly”? auto-hinter : Use the unpatented auto-hinter instead of the (recommended) TrueType bytecode interpreter bindist : Flag to enable or disable options for prebuilt (GRP) packages (eg. due to licensing issues) fontforge : Install internal headers required for TrueType debugger in media-gfx/fontforge (built with USE=truetype-debugger) utils : Install utilities and examples from ft2demos Which one of these constitute using freetype correctly? And/or, if “this should be documented properly” but you can’t be the one to do that, you could still write an explanatory line or two here so that I, or anybody else reading/finding this, would understand why a feature now missing from cairo is “nothing x11/cairo maintainers should” take care of. |
