| 2006-10-29 16:20:05 |
Frank Siegert |
description |
After a default Kubuntu installation, fonts look nicely anti-aliased and still clear (see attachment clear-before-appearance.png). But if I add a ~/.fonts.conf (and log out and in), they get completely blurry (see blurry-after-appearance.png), even if the ~/.fonts.conf is empty between <fontconfig> </fontconfig>. This caught me, because the Kubuntu system settings created a ~/.fonts.conf when I viewed the Appearance section (see the linked bug).
If you think it is a mistake to have a quasi empty ~/.fonts.conf present, or the one that Kubuntu System Settings writes out is wrong (see linked bug: fonts.diff), then this bug against fontconfig may be rejected. But I assume, that if one setting is not present in ~/.fonts.conf, it is taken from /etc/fonts/fonts.conf, so an "empty" ~/.fonts.conf should not hurt.
This bug seems to have been encountered by various users who have added their information to #63403. Especially comment 20 explains this, and the following comments also conclude, that maybe for mentioned case (3) there should be a separate bug filed. Maybe my bug report fulfills this need. |
After a default Kubuntu installation, fonts look nicely anti-aliased and still clear (see attachment clear-before-appearance.png). But if I add a ~/.fonts.conf (and log out and in), they get completely blurry (see blurry-after-appearance.png), even if the ~/.fonts.conf is empty between <fontconfig> </fontconfig>. This caught me, because the Kubuntu system settings created a ~/.fonts.conf when I viewed the Appearance section (see the bug #69085).
If you think it is a mistake to have a quasi empty ~/.fonts.conf present, or the one that Kubuntu System Settings writes out is wrong (see linked bug: fonts.diff), then this bug against fontconfig may be rejected. But I assume, that if one setting is not present in ~/.fonts.conf, it is taken from /etc/fonts/fonts.conf, so an "empty" ~/.fonts.conf should not hurt.
This bug seems to have been encountered by various users who have added their information to #63403. Especially comment 20 explains this, and the following comments also conclude, that maybe for mentioned case (3) there should be a separate bug filed. Maybe my bug report fulfills this need. |
|
