[Top][All Lists]

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

Re: [Fonts]X server crashes when looping on all fonts (fwd)

From: Fred Kiefer
Subject: Re: [Fonts]X server crashes when looping on all fonts (fwd)
Date: Sat, 05 Oct 2002 15:18:05 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.8) Gecko/20020204

This recommendation would force any user of GNUstep (using the xgps backend) to have a rather new release of the XFree86 X-Server installed. So we may not be able to go along this way, but as we already support the Xft extension as an additional option we could switch our font caching code for this specific environment over to the new enumeration interface. That way GNUstep would still support all old X implementations, while using the new interface where it is available and the user wants it. I have not looked into the new enumeration code, or rather I looked into it when I did write the Xft extension, but did not fully understand it at that time. Perhaps somebody is already familiar with this and can provide the code for a specific font cache tool for this environment.

We could take this as a chance to rework our current font caching as well, as this currently ignores the available font sizes and encodings, whcih should be used to allow for a better font selection, when the requested font is not available.


Nicola Pero wrote:

---------- Forwarded message ----------
Date: 30 Sep 2002 20:46:34 +0100
From: Juliusz Chroboczek <address@hidden>
Reply-To: address@hidden
To: address@hidden
Subject: Re: [Fonts]X server crashes when looping on all fonts

Hello, nice to hear from you again.

NP> The problem is an optimization -- the X server doesn't load a font
NP> until an app asks for information that can't be gotten from the
NP> XLFD list (xlsfonts doesn't crash the server).


NP> What's more, the server doesn't unload fonts after you're done with them,
NP> on the assumption that you'll need them later.

That's not true.  The memory is freed upon XFreeFont.

NP> If it's not a bug, then exactly what is the way/API for looping on all
NP> fonts in the system to get the info we need ?

There is widespread consensus (among at least five people) that the
current X11 font API is obsolete, and should not be used in new

The fact that you feel the need to loop accross all fonts at startup
simply shows that the needs of GNUstep go beyond what the core fonts
API provides.

I think you should consider using client-side fonts, the RENDER
extension, and the fontconfig/Xft2 API.  Please see Keith's masterwork
of propaganda on

Fonts mailing list

Gnustep-dev mailing list

reply via email to

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