x11-libs/cairo[cleartype] from portage is making the use of the cleartype patchset taken from ArchLinux. If we are using cleartype patches there, we should do it proper and add the cleartype patches for freetype and libXft too. The ebuilds with the related patches are attached, they are using the same patches as the *-cleartype font PKGBUILDS from archlinux. The patches are tested (for some time in devnull overlay now) and they provide a very nice font rendering indeed.
Created attachment 182953 [details] libXft-2.1.13.ebuild libXft-2.1.13.ebuild with cleartype useflag required patches: libXft-2.1.10-lcd-cleartype.diff
Created attachment 182954 [details, diff] libXft-2.1.10-lcd-cleartype.diff
Created attachment 182956 [details] freetype-2.3.8.ebuild freetype-2.3.8.ebuild with cleartype useflag required patches: 331-hmtx-no-shorts.diff freetype-2.2.1-memcpy-fix.patch freetype-2.2.1-subpixel-disable-quantization.diff freetype-2.3.2-enable-valid.patch freetype-bdflib-large-encodings.patch
Created attachment 182958 [details, diff] 331-hmtx-no-shorts.diff
Created attachment 182960 [details, diff] freetype-2.2.1-memcpy-fix.patch
Created attachment 182961 [details, diff] freetype-2.2.1-subpixel-disable-quantization.diff
Created attachment 182963 [details, diff] freetype-2.3.2-enable-valid.patch
Created attachment 182964 [details, diff] freetype-bdflib-large-encodings.patch
Comment on attachment 182963 [details, diff] freetype-2.3.2-enable-valid.patch that one already is in portage
Comment on attachment 182960 [details, diff] freetype-2.2.1-memcpy-fix.patch https://bugs.freedesktop.org/show_bug.cgi?id=6841 This is no longer a problem with ~arch poppler
Comment on attachment 182964 [details, diff] freetype-bdflib-large-encodings.patch This is a patch Debian has been lugging around since freetype 2.1.7, solving http://bugs.debian.org/302269 . We've never experienced it. If someone does, they can report in a seperate bug and we'll include and upstream the patch.
Comment on attachment 182958 [details, diff] 331-hmtx-no-shorts.diff This appears to be from here: http://www.mail-archive.com/freetype-devel@nongnu.org/msg01102.html And seems to be obsoleted here: http://www.mail-archive.com/freetype-devel@nongnu.org/msg01103.html For unknown reasons, debian is still lugging it along. *shrug* If the bug ever manifests here, we'll include the patch and upstream it.
That's _again_ no for libXft. I'll gladly accept the patch if upstream Xorg devs do too. See bug #254444. Thanks
So, did upstream has accepted the cleartype patch for cairo?
/*************************************************************************/ /* */ /* Define TT_CONFIG_OPTION_COMPONENT_OFFSET_SCALED to compile the */ /* TrueType glyph loader to use Apple's definition of how to handle */ /* component offsets in composite glyphs. */ /* */ /* Apple and MS disagree on the default behavior of component offsets */ /* in composites. Apple says that they should be scaled by the scale */ /* factors in the transformation matrix (roughly, it's more complex) */ /* while MS says they should not. OpenType defines two bits in the */ /* composite flags array which can be used to disambiguate, but old */ /* fonts will not have them. */ /* */ /* http://partners.adobe.com/asn/developer/opentype/glyf.html */ /* http://fonts.apple.com/TTRefMan/RM06/Chap6glyf.html */ /* */ #undef TT_CONFIG_OPTION_COMPONENT_OFFSET_SCALED
(In reply to comment #15) > #undef TT_CONFIG_OPTION_COMPONENT_OFFSET_SCALED Peter, as I read this comment this option changes handling of truetype fonts too and since mosts TT fonts are supposed to work (and are tested) in Windows I don't think it's good idea to enable this option. (In reply to comment #14) > So, did upstream has accepted the cleartype patch for cairo? Nico, yes and no. They commited it but then dropped, see: http://bugs.freedesktop.org/show_bug.cgi?id=10301 (In reply to comment #13) > That's _again_ no for libXft. I'll gladly accept the patch if upstream Xorg > devs do too. Does anybody reported this issue upstream? I've seen only message on mailing lists (very old) but URL to track on their bugzilla...
(In reply to comment #16) > (In reply to comment #15) > > #undef TT_CONFIG_OPTION_COMPONENT_OFFSET_SCALED > > Peter, as I read this comment this option changes handling of truetype fonts > too and since mosts TT fonts are supposed to work (and are tested) in Windows I > don't think it's good idea to enable this option. I concur. Closing. This was a bunch of random patches and the apple-rendering change.
