Raimund Steger wrote:
Behdad Esfahbod wrote:
On 14-08-18 08:58 AM, Raimund Steger wrote:
[...]
I understand this is mainly an effect of FC_COLOR priority being higher
than FC_FAMILY's?
Yes, that's where I'd put it. At least higher than the weak family
priority.
Though I don't expect some run-of-the-mill app/toolkit suddenly adding
color=true to all their patterns...
I was discussing whether it's possible for color-aware clients to specify
their capability. If they are to do that, they add color=true to all
requests.
Well, as you said, with a priority that high, advertising a capability
is not what the property will stand for. It's more like 'lang':
Overriding poor family choice of users.
i.e. we treat a glyph that is not rendered in color when it could be the
same way we would treat one that is not rendered at all (= as a box).
--
Worringer Str 31 Duesseldorf 40211 DE home: <rs@xxxxxxxx>
+49-179-2981632 icq 16845346 work: <rs@xxxxxxxxxxxxxxx>
_______________________________________________
Fontconfig mailing list
Fontconfig@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/fontconfig
