The quote from the document: use rgb sub-pixel ordering to improve glyph appearance on LCD screens. Changes affecting rendering, but not matching should always use target="font". So the following rule should be affected to the result of FcPattern for FcMatchFont: <match target="pattern"> <edit name="rgba" mode="assign"> <const>rgb</const> </edit> </match> but it does: $ fc-match -v | grep rgba rgba: 1(i)(s) This behavior messes up the rule of target="font". Aside from that, right now fontconfig warns when editing the user-defined object on target="scan" though, we should do it for others if it's not desirable and for target="pattern" and target="font" too.
(In reply to comment #0) > So the following rule should be affected to the result of FcPattern for > FcMatchFont: I meant "should NOT"
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/fontconfig/fontconfig/issues/41.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.