discuss-gnustep
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Problems with fonts.


From: Fred Kiefer
Subject: Re: Problems with fonts.
Date: Thu, 04 Nov 2004 22:20:35 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040114

Vaisburd, Haim wrote:
Fred Kiefer wrote:


defaults NSGlobalDomain GSFontAntiAlias YES
Hope this helps. Still we should try to get to the root of the real problem


The major problem of back-xlib was the lack of GSFontMask.
After I set it, this backend started to work. One can tell
it's a bug but I'm not concerned about it right now.


This is not so much a problem of xlib (it has its own problems though). What you did see is a problem of some X servers, when to many fonts get requested.

That backend complains about not having Helvetica, Times, and Fixed
(if I remember well) fonts in size 12.000 (but displays characters).
What does it mean? How to calm it down?


You seem to have rather unusual fonts installed. What you need to do is again to set some defaults to replace the standard font names with fonts available on your system. The keyes for the defaults are listed in the file NSFont.m (not sure if they are also in the defaults documentation as a developer I only use the source). What you need are NSFont and NSUserFixedPitchFont which explain the errors you get for Helvetica and Fixed, not sure about Times :-(


Also, it says

2004-11-04 01:49:42.000 PhotoClip[19034] Unable to initialize XIM, using standard keyboard events

What is this?

No idea.


The back-art is still broken, there I have problems with X itself, besides 
fonts:

2004-11-04 01:49:42.000 PhotoClip[19034] X-Windows error - BadValue (integer parameter out of range for operation)
          on display: :0.0
                type: 0
       serial number: 2669
        request code: 143


Again no idea. We used to have such errors a lot, but clean up of the frontend/backend interaction (no longer using X resources we did not allocate or already free) removed them all for me.

I looked into config.log, the only suspisious thing I saw
was it did not find glitz-glx (absolutely correct) but set
the corresponding #define as if I have it. I think compilation
did not even touch this thing.


You may savely ignore this, it is only used by the very bold ones that test the cairo backend.

Cheers
Fred




reply via email to

[Prev in Thread] Current Thread [Next in Thread]