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

List:       koffice
Subject:    Re: [BUG] KWord display text much too small
From:       Vadim Plessky <lucy-ples () mtu-net ! ru>
Date:       2001-09-07 8:53:55
[Download RAW message or body]

On Thursday 06 September 2001 11:06, Simon Hausmann wrote:
|   On Wed, Sep 05, 2001 at 10:59:52PM +0200, Thomas Zander wrote:
|   > On Wed, Sep 05, 2001 at 08:23:49PM +0200, Simon Hausmann wrote:
|   > > On Wed, Sep 05, 2001 at 12:39:54AM +0200, Nicolas Goutte wrote:
|   > > > On Tuesday, 4. September 2001 23:26, Thomas Zander wrote:
|   > > > > Are you using altialiased fonts? I know that that snapshot of
|   > > > > kdelibs had problems with always having antialiased fonts on, so
|   > > > > make sure that your vector fonts work before starting KWord ;)
|   > > > > And as X3 does not do font-antialiasing....
|   > > >
|   > > > Do you think that it is solved in kdelibs in the meanwhile?
|   > >
|   > > In which way was there a kdelibs bug with AA'ed fonts?
|   >
|   > In that I was unsuccesful to use fonts that were not vector fonts, in
|   > other words, I could not use non-AA.
|   >
|   > I still thing this is stupid; that as soon as I turn on AA the whole of
|   > KDE stops being able to use bitmapped fonts...
|   > This is a lot of fun when I had just one vector font, it was a script
|   > font ;)
|
|   Yes, could it be that Xft is limited to TrueType and Type1 fonts?
|
|   Do you experience the bug also with pure Qt applications? (like the qt
| examples)
|

Let me describe this bug (present already for a long time) in this way:
Some vector fonts (TrueType, PS Type1) available in Kword with AA enabled, 
*disappear* when you disable AA.
Typical occasion when in happens:
-XF 4.0.x or 4.1.x with video card not supporting AA (like old S3 Virge)
-XF 3.3.6 (which of course doesn't have AA / RENDER support)

From my experience, you need either TrueType or PostScript Type1 fonts in 
*non-unicode* format to reproduce it.
You can't demonstrate this problem with Arial and Times New Roman TTF (from 
Windows 98), as they are Unicode.

In case you want to test this problem and locate the bug, you can try these 
fonts from my computer (PFB, AFM, PFM):
http://kde2.newmail.ru/acadnewt-pfb.zip

Unzip them in PS Type1 fonts folder, then run #xftcache 
for AA environment. (it's enough to get them working with AA enabled)
For non-AA environment, add following lines in font.dir
---------------
6
acad55v4.pfb -paragraf-academycyr-medium-r-normal--0-0-0-0-p-0-iso8859-1
acad55v4.pfb -paragraf-academycyr-medium-r-normal--0-0-0-0-p-0-iso8859-5
acad55v4.pfb 
-paragraf-academycyr-medium-r-normal--0-0-0-0-p-0-microsoft-cp1251
newt55v4.pfb -paragraf-newton-medium-r-normal--0-0-0-0-p-0-iso8859-1
newt55v4.pfb -paragraf-newton-medium-r-normal--0-0-0-0-p-0-iso8859-5
newt55v4.pfb -paragraf-newton-medium-r-normal--0-0-0-0-p-0-microsoft-cp1251
---------------
As you see, there is no Unicode encoding, but with AA enabled, these fonts 
work fine in KWord :-)
Without AA, they just disappear :((
|
|   Simon
|   _______________________________________________
|   Koffice-devel mailing list
|   Koffice-devel@mail.kde.org
|   http://mail.kde.org/mailman/listinfo/koffice-devel

-- 

Vadim Plessky
http://kde2.newmail.ru  (English)
33 Window Decorations and 6 Widget Styles for KDE
http://kde2.newmail.ru/kde_themes.html
Do you have Arial font installed? Just test it!
http://kde2.newmail.ru/font_test_arial.html

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