Subject: proposal for gtk port: renaming fonts shipped with AW in order not to break Qt apps
From: Vlad Harchev (hvv@hippo.ru)
Date: Wed Jan 03 2001 - 10:56:52 CST
This proposal is relevant only to gtk port.
As everybody knows, the AbiWord wrapper script adds fonts AW ships to
fontpath before starting AW binary, and removes fonts from fontpath after
binary has exited. As it turned out, while fonts shipped with AW are in font
path, all freshly-started Qt-based apps (e.g. KDE apps) start to use different
(and ugly) font instead of the font they use when AW is not running.
Could someone confirm that this problem exists - i.e. that Qt apps really
start using ulgy font shipped with AW (since I was unable to reproduce this)?
If the problem really exists, we can rename xlfds of the fonts shipped with
AW, by prefixing them with Abi, i.e., 2nd line in fonts.dir shipped with AW
will change from
n019003l.pfa -AbiSource-Arial-regular-r-normal--0-0-0-0-p-0-iso8859-1
to
n019003l.pfa -AbiSource-AbiArial-regular-r-normal--0-0-0-0-p-0-iso8859-1
This will solve a problem with Qt apps.
In order to continue showing usual font names (e.g. "Arial" instead of
"AbiArial") to the user, we can make AW stripping "Abi" prefix of from the
font name in the xlfd, if this prefix is present.
This way, it will be safe to put fonts to fontpath permamently (and it won't
be necessary to remove font from font path too - that currently produces some
problem if several AWs are started in parallel).
What do you think about all this?
Best regards,
-Vlad
This archive was generated by hypermail 2b25 : Wed Jan 03 2001 - 11:24:16 CST