/etc/paludis/lcd-filtering.conf wrote:location = ${ROOT}/usr/portage/local/lcd-filtering
sync = tar+http://ogmrip.sourceforge.net/misc/gent ... ng.tar.bz2
sync_options = "--rsync-option=--exclude=profiles"
master_repository = gentoo
format = ebuild
names_cache = /var/cache/paludis/names
write_cache = /var/cache/paludis/metadata
Very good idea, thanks !!!! And I've just discovered that it's possible to do the same with layman !!!!Mr. Tao wrote:I’m glad I found this topic as I’ve used soor overlay which is not updated for a while. I’m going to test these patches right now. Meanwhile I’ve made repo definition for paludis
Code: Select all
<?xml version="1.0" ?>
<layman>
<overlays>
<overlay type="tar" src="http://ogmrip.sourceforge.net/misc/gentoo-lcd-filtering.tar.bz2" contact="billl@users.sourceforge.net" name="lcd-filtering">
<link>http://forums.gentoo.org/viewforum-f-12.html</link>
<description>LCD filtering</description>
</overlay>
</overlays>
</layman>Code: Select all
overlays : http://www.gentoo.org/proj/en/overlays/layman-global.txt
file:///etc/layman/lcd-filtering.xmlCode: Select all
layman -a lcd-filtering.


This might be obvious, but did you emerge fontconfig with the "ubuntu" USE flag enabled? The "newspr" flag only applies to libXft and cairo, while the "ubuntu" flag applies to freetype and fontconfig.yabbadabbadont wrote:Hmmm. Just tried it out and it doesn't seem like fontconfig-2.5.0-r1 is actually getting patched properly. The USE flags look correct and it compiled fine, but when portage ran the updates after emerge finished, it complained about "lcddefault" not being a valid fontconfig option... Then the cairo-1.6.4 ebuild failed complaining about LCD_* options not being defined, which leads me back to thinking that fontconfig isn't right.
I want to do some more investigating before I submit a proper error report. (one that actually has exact error messages instead of the crap I just listed.)


I'm guessing that you added all the packages to your /etc/portage/package.keywords, in which case you are not using the same versions as I listed in my post.mwhitlock wrote:Well the reason I asked is that it "works for me," so something must be different about your setup.yabbadabbadont wrote:I already stated that the USE flags looked correct... and if you look at the ebuilds, you will see that the correct ones are on by default.![]()

I have ACCEPT_KEYWORDS="~amd64" in my /etc/make.conf because I like running bleeding edge and don't mind reporting problems on bugs.gentoo.org.yabbadabbadont wrote:I'm guessing that you added all the packages to your /etc/portage/package.keywords, in which case you are not using the same versions as I listed in my post.
Code: Select all
[ebuild R ] x11-libs/cairo-1.6.4-r1 USE="X glitz newspr opengl svg -debug -directfb -doc -test -xcb" 0 kB [1]
[ebuild R ] x11-libs/libXft-2.1.13 USE="newspr -debug" 0 kB [?=>1]
[ebuild R ] media-libs/fontconfig-2.6.0-r2 USE="ubuntu -doc" 0 kB [?=>1]
[ebuild R ] media-libs/freetype-2.3.7 USE="X ubuntu -bindist -debug -doc -utils" 0 kB [?=>1]Code: Select all
=media-libs/fontconfig-2.6.0-r2
=media-libs/freetype-2.3.7
=x11-libs/cairo-1.6.4-r1
=x11-libs/libXft-2.1.12


Oh, thats cool, I did not know that. Is the tarball updated regularly?Mr. Tao wrote:I’m glad I found this topic as I’ve used soor overlay which is not updated for a while. I’m going to test these patches right now. Meanwhile I’ve made repo definition for paludis:/etc/paludis/lcd-filtering.conf wrote:location = ${ROOT}/usr/portage/local/lcd-filtering
sync = tar+http://ogmrip.sourceforge.net/misc/gent ... ng.tar.bz2
sync_options = "--rsync-option=--exclude=profiles"
master_repository = gentoo
format = ebuild
names_cache = /var/cache/paludis/names
write_cache = /var/cache/paludis/metadata

Ok I'm curios how long it will lastbi3l wrote:Almost as soon as there is a new version of either cairo, libXft, freetype or fontconfig in portage.Phlogiston wrote:Oh, thats cool, I did not know that. Is the tarball updated regularly?

please add profiles/repo_name.Mr. Tao wrote:I’m glad I found this topic as I’ve used soor overlay which is not updated for a while. I’m going to test these patches right now. Meanwhile I’ve made repo definition for paludis:/etc/paludis/lcd-filtering.conf wrote:location = ${ROOT}/usr/portage/local/lcd-filtering
sync = tar+http://ogmrip.sourceforge.net/misc/gent ... ng.tar.bz2
sync_options = "--rsync-option=--exclude=profiles"
master_repository = gentoo
format = ebuild
names_cache = /var/cache/paludis/names
write_cache = /var/cache/paludis/metadata
Code: Select all
paludis@1219682970: [QA e.repo_name.unusable] Couldn't open repo_name file in '/usr/local/portage/lcd-filtering/profiles/', falling back to generated name 'x-lcd-filtering' (ignore this message if you have yet to sync this repository).

LCD subpixel filtering using FreeType
- -------------------------------------
FreeType 2.3.5 added support for various LCD subpixel filtering, and
fontconfig 2.6.0 added support for configuring LCD filter on a font by font
basis. Cairo now relies on FreeType and fontconfig for subpixel filtering.
This work is based on David Turner's original patch to cairo, maintained
and tested by Sylvain Pasche and others. Thanks all!
Qt does not use Cairo.mwhitlock wrote:Does this mean we soon won't need cairo in the overlay? Now if only libXft would pick up the slack!aronparsons wrote:Cairo now relies on FreeType and fontconfig for subpixel filtering.
Does anyone know if Qt4 uses Cairo?


I have the Last.fm player installed, and it uses Qt4, and its fonts look identical to those of the rest of my system, so I would guess that Qt4 refrains from messing with the glyphs it receives from FreeType, which means they remain properly filtered for LCD.kokoko3k wrote:What about kde4 and/or qt4?
As far as i know, qt4 doesn't use cairo nor Xft.
Sad, but no lcd font rendering for now.Note also that the code that had been in cairo 1.7.x calling into
freetype's optional lcd_filter function was removed from cairo before
the 1.8.0 release. We do expect this code to come back in some form in
the future.
Remove all lcd_filter code.
We reverted the public API for setting lcd_filter font options back in 1b42bc8033bc , but we had left the implementation which would examine fontconfig and Xft properties for the option, and which would call into freetype for subpixel glyph rasterization. However, I recently realized, (and the test suite had been trying to tell me for a while), that this approach would cause a regression for users who were previously using sub-pixel text, but without sub-pixel rendering built directly into freetype. That's not acceptable, so all the code is coming out for now.