You are not logged in.
Hi, I always used lcdlegacy filter for my dejavu fonts:
<match>
<edit name="dpi"> <int>96</int> </edit>
<edit name="antialias"> <bool>true</bool> </edit>
<edit name="autohint"> <bool>false</bool> </edit>
<edit name="hinting"> <bool>true</bool> </edit>
<edit name="hintstyle"> <const>hintslight</const> </edit>
<edit name="rgba"> <const>rgb</const> </edit>
<edit name="lcdfilter"> <const>lcddefault</const> </edit>
</match>
<!-- DejaVu looks crispier with lcdlegacy -->
<match target="font">
<test name="family" compare="contains"> <string>DejaVu</string> </test>
<edit name="hintstyle"> <const>hintfull</const> </edit>
<edit name="lcdfilter"> <const>lcdlegacy</const> </edit>
</match>
And also, since the last year:
export FREETYPE_PROPERTIES='truetype:interpreter-version=35'
Today, after upgrading all my packages, both lcddefault and lcdlegacy are rendering exactly the same. I can ensure that the font configuration is being taken into account, since disabling antialias, autohinting, etc. does have a visible effect.
Any ideas?
Thank you in advance, Carlos.
Offline
I can say than downgrading freetype2 from 2.8-2 to 2.8.1-1 fixes the above issue. I'm not marking this as solved yet, since this is not really a solution. But I'm reporting this as a package bug (maybe it's an upstream one, I don't know). Any further useful information will be very much appreciated.
Offline
Offline
I'm not quite sure yet but I indeed suspect it's an upstream problem due to the nature of the changes introduced by 2.8.1, so I've reported it to the freetype team also. They've requested me to test the issue using HEAD, so I'm going to inform about the results here as soon as I do the test.
Offline
Well, cleartype is disabled by default now, so forget about filters except that you are willing to maintain an alternative aur package.
If you're interested in some discussion and ranting regarding this issue: http://savannah.nongnu.org/bugs/?52124
I'm sticking to 2.8 until I decide to create a freetype2-cleartype package.
Offline