>> (I always considered the significantly simpler approach being enough:
>> the user in enabling TWM_USE_XFT voluntarily passes "the point of no
>> return"; if xft-font problems arise, then these are to be solved.)
> Well, that's the point.  As you have it, the end user does _not_ in fact 
> decide on TWM_USE_XFT.  The distributor does.
> Marc.

I not quite sure if this is the essential point in our case who and how
compiles twm, but which fonts are installed and what stands in
system.twmrc for a user not wishing to touch the default,
distributor-provided configuration.

Having not verified, but I strongly suspect if starting the unmodified
twm having first removed the 'misc/' font directory entirely, then X is
not going to find 'fixed', and as of now, twm refuses to start. It
appears, 'fixed' is an alias to something like
according to misc/fonts.alias;  and the key is, this name is XLFD compliant.

So, luckily we are now a step closed to the solution:  let's not use
'fixed' as coded-in-default in twm.c if TWM_USE_XFT is defined, but
'-*-fixed-*-*-*-*-*-*-*-*-*-*-*-*', and neither XListFonts() nor
XftFontOpenXlfd() have any further difficulties!  (Is XListFonts()
supposed to translate font alias names at all?)  This looks a good idea,
in fact this is what you suggested first: let XListFonts() resolve
'fixed' and then use it.  Now we know how to do that. :-)

(As a backside, we then remove the flexibility in twm to use the
'fixed'-alias-redirection to an arbitrary font.)


    Eeri Kask

P.S. We could use some better initialisation for 'fixed' as above, maybe
'-*-fixed-medium-r-normal--*-100-*-*-*-*-iso8859-1' or whatever.
Devel mailing list

Reply via email to