[Bug 904015] outlined fonts didn't get their antialias enabled by fontconfig in openSUSE 13.2 and above
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=904015
http://bugzilla.suse.com/show_bug.cgi?id=904015#c39
--- Comment #39 from Petr Gajdos
Hi, Petr,
Do you mean this:
pattern: many fonts -> edit -> edited many fonts -> match -> matched fonts font: many fonts -> match -> matched fonts -> edit -> edited matched fonts
((1)) pattern at the beginning is a request. For example, in $ fc-match -v sans:size=20 the pattern is 'sans:size=20' Fontconfig first applies <match target="pattern"> rules to this pattern, fx. <match target="pattern"> <test qual="any" name="family"> <string>sans</string> </test> <edit name="family" mode="assign" binding="same"> <string>sans-serif</string> </edit> </match> _edits_ sans to sans-serif. the pattern is then 'sans-serif:size=20'. Later, it applies <alias> [which is just syntactic sugar to <matrch target="pattern">] rules, e. g. from 60-family-prefer.conf. The pattern then looks for example like: "Roboto 'Noto Kufi Arabic' ... sans-serif ...":size=20' etc. These changes has to be done before matching. ((2)) Match. According to pattern created in ((1)), one font is chosen from the system. The pattern is filled in with final entries, e. g. file, charset, etc. ((3)) Now <match target="font"> rules are applied. For example rendering algorithm details need to be resolved here in my opinion as they depend on e. g. fontformat. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com