Skip to content

objects for target="pattern" is inherited to the result of FcMatchFont

Submitted by Akira TAGOH @tagoh

Assigned to fon..@..op.org

Link to original bug (#53323)

Description

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.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information