Bug#398236: closed by Fathi BOUDRA <fabo@debian.org> (reply to fabo@debian.org) (libqt4-gui: No Anti-Aliased fonts since 4.2)
Debian Bug Tracking System wrote:
This is an automatic notification regarding your Bug report
which was filed against the libqt4-gui package:
#398236: libqt4-gui: No Anti-Aliased fonts since 4.2
It has been closed by Fathi BOUDRA <fabo@debian.org> (reply to fabo@debian.org).
Why are you closing the bug? There is no explanation!
Anyway, here's an interesting IRC session:
<Quibus> Hi, is it normal that a Qt app looks bad on my GNOME system,
in the sense that the fonts are not anti-aliased? (All other fonts are.)
<peppe> Quibus: http://pastebin.com/m7a39e433 add this to ~/.fonts.conf
The contents of the file:
<?xml version="1.0"?><!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>
<!--
<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>
</fontconfig>
<Quibus> can you give some explanation why this is necessary?
<peppe> maybe you have also to remove the rgba stuff (rgb -> none) if
you don't want to have subpixel antialiasing
<Quibus> Can you give me the somewhat longer answer? :-)
<peppe> because GNOME suck^W doesn't use .fonts.conf (as every other
toolkit that uses fontconfig do) , but keeps its font antialiasing
configuration somewhere in its windows registr^W^W gconf stuff
<Quibus> so far for freedesktop.org standards?
<Quibus> Anyway, thanks peppe
<peppe> maybe with Qt4.5 and QGtkStyle this behaviour will end, but
if I use another toolkit that uses freetype, I won't get antialiased
fonts on that
<peppe> I don't know which one is "correct" by freedesktop.org
standards, but saying "yeah, keeping configuration in GConf is the
standard" is a bit strange
Anyway, this did fix the problem (again) for me. Might be a good idea to
keep this information alive, as it isn't documented on a clear
location... (AFAIK).
--
Grtjs, Manuel
PS: MSX FOR EVER! (Questions? http://faq.msxnet.org/ )
PPS: Visit my homepage at http://manuel.msxnet.org/
Reply to: