[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    Bug#24485: new infos?
From:       David Faure <david () mandrakesoft ! com>
Date:       2001-05-01 1:32:13
[Download RAW message or body]

On Monday 30 April 2001 21:10, Thorsten Schnebeck wrote:
> Hi David, hi Magnus!
> 
> Are there some new Infos relating to this "showstopper"? It's still there in 
> latest CVS and I don't find any discussions on the mailing-lists.

I'm just back from an extended weekend, so I haven't looked into
how to fix this yet.

> David, why does KOffice makes his own resolution calculations? 

To get it right :). Really, before kword, no KDE app was showing
you a page on screen that has the same size as the real paper page.

> Does this mean a 12-point font in KWord at 100% looks bigger or smaller than a 12-point in 
> Kate, why? 

No, they should appear the same. But the main difference is that Kate only cares
about the font size, whereas KWord also care about the paper size, the size
of the frames, pictures, etc. That's why KWord has to use the x11 DPI
setting, whereas kate simply uses Qt.

My quick investigation about this problem is that it's QFont that
does VERY nasty things when printing, to workaround the fact that
applications usually don't care... but this goes against KWord's
"zooming before printing" stuff. Will have to find a way.

> If somebody want a correct dependency between screen and paper 
> he/she can start X with e.g. "startx -- -dpi [DPI]". 

Yes, exactly. But that's not enough. The apps have to use that DPI setting.
Qt does, for fonts. KWord has to do it too, for _everything_.
The problem is getting KWord to use Qt's font stuff correctly.

-- 
David FAURE, david@mandrakesoft.com, faure@kde.org
http://perso.mandrakesoft.com/~david/, http://www.konqueror.org/
KDE, Making The Future of Computing Available Today

[prev in list] [next in list] [prev in thread] [next in thread]