Re: [Fontforge-users] bug asking for existing bpg-courier - very weird

[Paulo S. <nit...@gm...>]

thanks, it's working now - but btw, it's a problem a bit annoying for
users, specially newbies (like graphic designers, working daily on
typeface designing, and doesn't feel that comfortable on debugging...)
- and it seems to be very common, as i could find from Google...
http://www.google.com/search?q=Help%21+Server+claimed+font&ie=utf-8&oe=utf-8&aq=t&rls=org.debian:en-US:unofficial&client=iceweasel-a

thanks again, and cheers! =)

On 1/17/09, Paulo Silva <nit...@gm...> wrote:
> the another problem of debuging fonts.dir files is there are too many
> - and hard to be accurated on seeking if the problem is found or not
>
> Is there some comfortable way to check this, like using a simple bash
> or python script? like a 'for i in fontsdir grep something' or
> whatever? My suggestion is Fontforge coming with this sort of
> debugging tool or script... just a suggestion...
>
> thanks! =)
>
>
>
> On 1/17/09, Paulo Silva <nit...@gm...> wrote:
>> thanks, i'll try again
>>
>> btw, i have an idea (i don't know how to implement it in the Fontforge
>> sources) - for avoiding this bug, would be interesting if the
>> Fontforge code, when opening, and looking for these fonts, having some
>> kind of exceptions (a simple solution for it) allowing to bypass these
>> situations, and allowing Fontforge being running, even with these X
>> server problems?
>>
>> thanks a lot again! =)
>>
>> On 16 Jan 2009 15:10:08 -0800, George Williams <gw...@si...> wrote:
>>> On Tue, 2009-01-13 at 09:22, Paulo Silva wrote:
>>>> Hi!
>>>> I'm trying now to run Fontforge (i use it a lot!), but
>>>>
>>>> guest@macbook:~$ fontforge
>>>> Copyright (c) 2000-2008 by George Williams.
>>>>  Executable based on sources from 00:29 GMT 29-Apr-2008.
>>>>  Library based on sources from 20:49 GMT 30-Apr-2008.
>>>> Help! Server claimed font
>>>> 	-bpg-courier-medium-r-normal--16-0-0-0-p-0-iso10646-1
>>>>  existed in the font list, but when I asked for it there was nothing.
>>>>  I may crash soon.
>>>> Segmentation fault
>>> This means your font configuration is wrong.
>>>
>>> The X server thinks it has a font
>>>   -bpg-courier-medium-r-normal--16-0-0-0-p-0-iso10646-1
>>> because there is a fonts.dir file somewhere in your font path which says
>>> so. Now the fonts.dir file contains a mapping between X font names and
>>> font files on the system. If the font file does not exist, then the
>>> server can't load the font, it returns a failure when fontforge tries to
>>> load it.
>>>
>>> Now since fontforge has already asked the server whether the font exists
>>> (and has been told it does) it gets very confused when the server later
>>> says it does not exist.
>>>
>>> The solution is to fix your X configuration.
>>>
>>> Search through all the fonts.dir files on your system and find the one
>>> which defines this font, and remove this line (or correct it so that it
>>> points to a real file).
>>>
>>>> Another question: if some coders may help to recode the actual
>>>> motif-like gui (which i respect, for nostalgic and historical reasons)
>>>> with gtk or wxWidgets, would help problems like this not being
>>>> persistent in a future?
>>> Feel free to do this. No one else wants to, but if you do, go right
>>> ahead.
>>>
>>>
>>
>