Yeah, now that I look at the file, it seems like the UnixFontPath
setting is always relative to the ABISUITE_HOME environment variable
(set by the wrapper shell script). This wasn't always the case;
when the Type 1 font support was added, it read ABIWORD_FONTPATH
from the environment, but I believe that has been removed now.
You could dig through the prefs code to see how it's loading it.
It shouldn't be too hard to allow more flexibility in the font
path.
> What I'm kinda checking into is having it look at X's different font
> paths and fonts.dir's and then seeing whether or not the type 1 font has
> a .afm file to go along with it. The main problem would be the the
> amount of time for people like me who go a little overboard when they
> install a trillion fonts.
I think that would be a nice feature, but the problem is that X's
font path is not necessarily the application's font path.
When the application is remotely displayed, X font paths won't
always resolve to anything on the client (AbiWord) side. It's
still a problem right now, but can be solved by using AbiWord's
fonts through a font server or by having a local copy.
-- Shaw Terwilliger