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

List:       koffice-devel
Subject:    Re: CC: Re: "new" wp for linux
From:       David Faure <dfaure () klaralvdalens-datakonsult ! se>
Date:       2004-04-13 22:21:55
Message-ID: 200404140021.55610.dfaure () klaralvdalens-datakonsult ! se
[Download RAW message or body]

On Wednesday 14 April 2004 00:09, Tomasz Grobelny wrote:
> On Tuesday 13 of April 2004 23:34, James Richard Tyrer wrote:
> > There is an additional issue with Printer rendering that KWord and/or Qt
> > must know the resolution of the printer.
> > My best guess is that KWord-1.3 is currently using Printer rendering so
> > there are still slight problems.
> I doubt it since Qt prints through postscript files and that means it has no 
> knowledge about destination printer.
There are case where you can fine the resolution of the destination printer
(via QPrinter or KPrinter), but that doesn't always help anyway (worst example
is printing to a .ps file and then printing to any printer you want).

Lars suggested to just use a high enough DPI so that it looks ok on
any printer - if we get it to work we could even make it configurable,
to differenciate between normal office use (600 DPI?) and professional
use (1200 DPI or more).

But I tried doing that long ago in KWord and it didn't work well with
embedded objects, since it requires that all koffice applications really
support zooming (in paintContent at least) so that one can zoom out
after setting the DPI to a very high value (to end up with the right
size after all).

> > That is, for KWord to work correctly, Qt needs to add what I have called
> > PostScript font rendering.
> And that means redesigning entire set of painting/font classes :-(. Why? 
> Because:
> -Qt sets fixed width of strings in postscript files,
What else would it do?

> -QFont(Metrics) gives inaccurate metrics information,
That's what I hope Qt4 fixes.

> -you can't order Qt to use only scalable fonts
Actually Lars said ForceOutline should do that, and if it doesn't do it
then it's a bug. We use ForceOutline in kotext, not sure if it makes
a difference though.

-- 
David Faure -- faure@kde.org, dfaure@klaralvdalens-datakonsult.se
Qt/KDE/KOffice developer
Klarälvdalens Datakonsult AB, Platform-independent software solutions
_______________________________________________
koffice-devel mailing list
koffice-devel@mail.kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel

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