On 2010-07-12, Allan Gottlieb <[email protected]> wrote:

>>> What does C-u C-x = give on your system
>>
>>         character: b (98, #o142, #x62)
>> preferred charset: ascii (ASCII (ISO646 IRV))
>>        code point: 0x62
>>            syntax: w         which means: word
>>          category: .:Base, a:ASCII, l:Latin, r:Roman
>>       buffer code: #x62
>>         file code: #x62 (encoded by coding system nil)
>>           display: no font available
>>
>>> and do you have that font available?
>>
>> No, I don't seem to have 
>> Sans-normal-normal-normal-*-20-*-75-75-*-0-iso10646-1
>> availble according to xfontsel.
>
> Three points
>
> 1.  Did you build emacs with xft support?
>
> 2.  The name you give "Sans-normal-normal-normal-*-20-*-75-75-*-0-iso10646-1"
>     looks to be just the suffix  did you mean something like
>     "-unknown-DejaVu Sans-normal...".

Oops -- cut/paste error.

I don't have that font using the whole pattern either.

> You don't need to have DejaVu, but I would advise getting either
> DejaVu or bitstream vera.

I guess I can install more fonts, but I was hoping I could point emacs
at one of the rougly 4000 I've already got.

> 3.  Your output and mine differ in one point (before the font issue)
>     You have "coding system nil". I have "coding system utf-8-unix".
>     Unfortunately I know very little about coding systems but do
>     wonder why ours are different since we both did emacs -q.
>     Unfortunately if we do emacs -Q to eliminate some system
>     customization, there is no splash screen.  The description of
>     UTF-8 says it is for unicode.  Perhaps your nil coding system has
>     trouble with unicode, but I am afraid this has gotten outside my
>     expertise.

I do have one computer where emacs does find a font for the "about"
screen, so I guess it's a matter of comparing the two.

-- 
Grant Edwards               grant.b.edwards        Yow! Will it improve my
                                  at               CASH FLOW?
                              gmail.com            


Reply via email to