FEATURE: Forcing DPI setting for fonts

[Lubos Lunak]

 Hello,

 this is basically http://bugs.kde.org/show_bug.cgi?id=111754 for the 3.5.x 
branch. Or just google for things like 'kde gnome fonts dpi' to get more info 
about the issue, like 
http://process-of-elimination.net/wiki/Control_Font_DPI_in_X . In short, most 
fonts are designed only for 96DPI and 120DPI and look horribly with other 
DPIs. Since X by default computes real DPI and we just use it, while GNOME 
forces it to 96DPI, we get a lot of "KDE has ugly fonts", despite us doing 
things "properly". Go figure.

 The patch adds a combobox allowing to force DPI this way, but it still 
defaults to real DPI.

>  The requirements for a new feature to get in KDE3.5.x are:
>
> - it needs to be already in trunk - we already have lot of code that went
> only into KDE3.5.x and not trunk, no need to make this even worse

 check

> - it needs to be complete and ready - don't ask "I plan to develop this
> feature for 3.5.x, will it get in?"

 check

> - it needs to be well-tested - create a branch or a patch and have it
> tested by other people, or even make independent public releases
> (kde-apps.org, in some distribution packages, whatever)

 Well, this one is so simple that I don't think it really needs that much 
testing. Still, I'm posting this mainly just in case somebody sees some 
problem with messing with the DPI this way.

>
> - it needs to respect other freezes - if no new i18n messages are allowed,
> no feature changing those is allowed either

 3 small i18n strings

> - it needs to be committed no later than a month before the next release is
> tagged (right now there's no date for 3.5.3, but presumably all releases
> will be announced at least a month in advance)
>
> - it must be mentioned in the changelog of the release (marked with "New:")
>
> - commit log must include "approved by ..." and don't forget the FEATURE:
> tag where applicable
>
> - last and the most important: It must be posted to the mailing list for
> the SVN module (kde-core-devel for those without) and must be approved by
> the module's maintainer (TWG for those without)

 pending, pending, pending, pending



 PS: There's also still pending my other patch with caching of wallpapers 
(http://lists.kde.org/?l=kde-core-devel&m=114502950321763&w=2) that went 
without any reaction at all. Should I take that as a permanent no? The latest 
version of the patch is attached.

-- 
Lubos Lunak
KDE developer
--------------------------------------------------------------
SUSE LINUX, s.r.o.   e-mail: l.lunak at suse.cz , l.lunak at kde.org
Lihovarska 1060/12   tel: +420 284 028 972
190 00 Prague 9      fax: +420 284 028 951
Czech Republic       http//www.suse.cz
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fonts_dpi.patch
Type: text/x-diff
Size: 5460 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20060825/4469c7df/attachment.patch>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 09_cache_wallpapers.tar.gz
Type: application/x-tgz
Size: 16407 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20060825/4469c7df/attachment.bin>