Thanks for all the replies. That has helped me to see the things clearer :-)<br><br clear="all">Lukas Sommer<br>
<br><br><div class="gmail_quote">2011/6/17 Alexey Zinovyev <span dir="ltr"><<a href="mailto:alzinovyev@gmail.com">alzinovyev@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 17.06.2011 14:44, Lukas Sommer wrote:<br>
>> GTK/Qt don't use XFT at all.<br>
><br>
> That's interesting. I didn't know this. However, at least the KDE font<br>
> settings module changes the Xft.dpi value. Maybe fontconfig makes use of<br>
> this one? So maybe this should be switched to use directly fontconfig?<br>
><br>
> Lukas Sommer<br>
><br>
><br>
</div>It's documented behavior.<br>
<a href="https://wiki.archlinux.org/index.php/Font_Configuration#Distorted_fonts" target="_blank">https://wiki.archlinux.org/index.php/Font_Configuration#Distorted_fonts</a><br>
says that fontconfig defaults to Xft.dpi but has it's own DPI setting in<br>
fonts.conf (and it works for all GTK/Qt software).<br>
Qt doesn't depend on Xft (at least in my distro). GTK+ does, but only<br>
for deprecated pango-xft backend.<br>
Xft is still needed in other toolkits (like Tk) and in some pure Xlib<br>
software (dzen2, xterm, rxvt).<br>
</blockquote></div><br>