On Thu, Dec 13, 2012, at 01:05 AM, Raimund Steger wrote:
> At first glance it looks like you assign antialias=true with a
> target="font" rule. This is applied later than any target="pattern"
> rule.
Since "pattern" rules are applied before "font" rules, I applied the
default setting as a "pattern" rule. The docs don't explain how to do a
wildcard match, so I used an empty string. It seems to work. Is this the
correct way to do it? Would it be better to just omit the <test>?
The lower block is now a "font" rule, but it still has no effect. I am
testing it by setting gedit to display with the Monospace font.
-------------------------------------------------------------------------------------------
<?xml version='1.0'?>
<!DOCTYPE fontconfig SYSTEM 'fonts.dtd'>
<fontconfig>
<match target="pattern">
<test name="family"><string></string></test>
<edit mode="assign" name="rgba"><const>rgb</const></edit>
<edit mode="assign" name="embeddedbitmap"><bool>true</bool></edit>
<edit mode="assign" name="autohint"><bool>false</bool></edit>
<edit mode="assign" name="hinting"><bool>true</bool></edit>
<edit mode="assign" name="antialias"><bool>true</bool></edit>
<edit mode="assign"
name="lcdfilter"><const>lcddefault</const></edit>
<edit mode="assign" name="hintstyle"><const>hintfull</const></edit>
</match>
<match target="font">
<test name="family"><string>Monospace</string></test>
<edit mode="assign" name="antialias"><bool>true</bool></edit>
</match>
</fontconfig>
-------------------------------------------------------------------------------------------
--
http://www.fastmail.fm - The professional email service
_______________________________________________
Fontconfig mailing list
Fontconfig@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/fontconfig
