Subject: Re: abiword script shouldn't add font when it already exists
From: Bryce Nesbitt (bryce@obviously.com)
Date: Fri Jan 18 2002 - 12:10:27 CST
Tomas Frydrych wrote:
>
> > Well, I don't believe so at least :-) Here is a patch to check to see
> > if the font path exists before adding it (please excuse me if there is
> > a better way to do this but my shell is appalling).
>
> We are not meant to set font path from the wrapper script any
> more, this is now done from within xap_UnixFontManager.cpp,
> which means you can, at least in prinicple, run the executable
> without the wrapper. The xset -fp line should have been commented
> out; it is my oversight it was not, and I have just fixed it.
Just for the record: modifying the global unix font path on the
fly while AbiWord is running means that other applications operate
differently, depending if Abi is running. This is highly unusual
in the Unix world.
See bugs:
http://bugzilla.abisource.com/show_bug.cgi?id=1030
http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=18855
http://bugzilla.abisource.com/show_bug.cgi?id=2598
The first one is the top voted non-enhancement bug.
-Bryce
PS: Also note (as is well know to the developers) that the xset trick
does not work on RedHat Linux.
This archive was generated by hypermail 2b25 : Fri Jan 18 2002 - 12:10:43 CST