From kde-devel  Sun Aug 03 12:32:40 2003
From: Craig Drummond <Craig.Drummond () gmx ! net>
Date: Sun, 03 Aug 2003 12:32:40 +0000
To: kde-devel
Subject: Re: Fonts ... ARGH!!!
X-MARC-Message: https://marc.info/?l=kde-devel&m=105991410419080

> Craig Drummond has apparently changed his code so that it adds various
> aliases for the font.  That is, the first four entries for each family are
> the correct PostScript font names.  These are followed by various
> variations as a work around for the fact that KWord (and probably other KDE
> applications) doesn't get the PostScript font names correct.
>
> He has done a good job, but I don't think that this is the way to do it. 
> Why is it that if his code can get the correct PostScript font names then
> why can't other KDE applications get the correct names?  IIUC, the
> FreeType2 library will get the PostScript name for you if you have told it
> where the font is.  And that XFT[2]/FontConfig will tell you the location
> of the font.

The reason being not every app is compiled against FreeType2. KDE and Qt don't 
require FreeType/Xft as far as I'm aware. Hence the aliases are neccessary.

My code can read the PS name as I read the actual .ttf files - Qt/KDE do not.

Perhaps you should file a bug report with Qt? ie. get them to try and open the 
TTF file to get the real PS name if the font is not embedded.

> Or perhaps someone just doesn't realize that the "Full Font name" and the
> "Postscript name" are NOT the same -- you can't just remove the blanks.

Nope. I don't think fontconfig access the PS name, hence the aliases will be 
required. But I guess you can get this via the method above.

Craig.
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<