Comment # 46 on bug 904015 from Marguerite Su

Hi, Petr,

Breaking news! I got it reproduced!

First, I followed your instruction in comment#45 on a 1320 box, but the looking
is still good, and is exactly what you/the reporter want.

Second I cleaned up all your stuff. And I emulated the reporter's setting.

So I got it reproduced. (see attachment in the next comment)

It turns out that KDE will add these lines into
~/.config/fontconfig/fonts.conf:

 <match target="font">
  <edit mode="assign" name="rgba">
   <const>rgb</const>
  </edit>
 </match>
 <match target="font">
  <edit mode="assign" name="hinting">
   <bool>true</bool>
  </edit>
 </match>
 <match target="font">
  <edit mode="assign" name="hintstyle">
   <const>hintfull</const>
  </edit>
 </match>
 <match target="font">
  <edit mode="assign" name="antialias">
   <bool>true</bool>
  </edit>
 </match>
 <match target="font">
  <test compare="more_eq" name="size" qual="any">
   <double>0</double>
  </test>
  <test compare="less_eq" name="size" qual="any">
   <double>8</double>
  </test>
  <edit mode="assign" name="antialias">
   <bool>false</bool>
  </edit>
 </match>
 <match target="font">
  <test compare="more_eq" name="pixelsize" qual="any">
   <double>0</double>
  </test>
  <test compare="less_eq" name="pixelsize" qual="any">
   <double>11</double>
  </test>
  <edit mode="assign" name="antialias">
   <bool>false</bool>
  </edit>
 </match>

It is intended. If I cleaned these settings. The "Fonts" section of KDE
Settings
will be reset too.

And the 0-11 antialias false is intended too. Not done by myself or my fault
operations. 

That is you exclude range 0-8, KDE will automatically add another 0-11 entry
for you.

And "fc-match -v Tahoma:size=8" returns:

    size: 8(f)(s)
    pixelsize: 8.33333(f)(s)
    antialias: False(w)
    hintstyle: 3(i)(w)
    hinting: True(w)
    autohint: False(w)

The "antialias" is false here.

Remove the local fonts.conf, then:

    size: 8(f)(s)
    pixelsize: 8.33333(f)(s)
    antialias: True(w)
    hintstyle: 3(i)(w)
    hinting: True(w)
    autohint: False(w)

And I successfully isolated the problem lays here:

 <match target="font">
  <test compare="more_eq" name="size" qual="any">
   <double>0</double>
  </test>
  <test compare="less_eq" name="size" qual="any">
   <double>8</double>
  </test>
  <edit mode="assign" name="antialias">
   <bool>false</bool>
  </edit>
 </match>

KDE's implementation of "exclude range" actually excluded the edge values too.

Maybe in 13.1, the implementation was not.