Like some others, I also object to keeping the "legacy" filter as the default. Freetype doesn't call it legacy without reason: it is optimized for one special rendering preference, full native hinting (IMO it's doing badly even in that case), and is crap in all others. Moreover, if the fonts do not have high-quality hinting instructions, it does a bad job as well. I think this isn't even subjective, the color fringing of the "legacy" filter is bad regardless of display and/or personal preferences.
If you still think it matters to not "surprise" users (I certainly would call improved text rendering a good surprise, though), the FIR3 filter might be a good choice for the default, but I'd surely go for the default (FIR5) by default. This is how it should be anyway. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/164640 Title: Build Firefox 3 against a subpixel-patched cairo Status in Fontconfig - Font Configuration Library: Fix Released Status in libcairo - cairo vector graphics library: Confirmed Status in fontconfig package in Ubuntu: Fix Released Status in libcairo package in Ubuntu: Fix Released Status in xulrunner-1.9 package in Ubuntu: Fix Released Bug description: Binary package hint: firefox-3.0 In Ubuntu 7.10 and newer, Firefox 3.0 looks out of place with subpixel rendering enabled, due to the fact that it uses an unpatched, bundled version of Cairo. The patch should be ported to Cairo 1.5 and applied in the firefox-3.0 package. To manage notifications about this bug go to: https://bugs.launchpad.net/fontconfig/+bug/164640/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp