[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: MULE shows gibberish; now what?
From: |
Kenichi Handa |
Subject: |
Re: MULE shows gibberish; now what? |
Date: |
Thu, 10 Oct 2002 10:51:02 +0900 (JST) |
User-agent: |
SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/21.1.30 (sparc-sun-solaris2.6) MULE/5.0 (SAKAKI) |
In article <address@hidden>, "Stefan Monnier" <monnier+gnu/address@hidden>
writes:
>> To get those properties, we must call XListFontsWithInfo
>> which, I think, is very slow compared with XListFonts.
>> Perhaps, we must introduce a variable, for instance,
>> `unreliable-font-registry-encoding-name-list, use
>> XListFontsWithInfo only to find a font whose
>> registry-encoding matches with this variable.
> I was indeed thinking that it would probably be too costly preformancewise.
> Although maybe we could do a sanity-check late in the game (after we have
> settled on a particular font) and if the sanity check fails, we add
> the fontname to face-ignored-fonts and try again.
Ah, yes, that method is less costy.
>> Is that intention different from this?
>>
>> (dolist (fontset (fontest-list))
>> (set-fontset-font fontset 'cyrillic-iso8859-5
>> '("etl-fixed" . "iso8859-5")))
> No, that sounds just right. But I think such things should be
> documented in the Emacs Manual (and thus understandable to someone
> who's not proficient in ELisp).
Isn't such a thing too cryptic to go in Emacs Manual.
It's a long term todo item to provide a good cutomization
method of font related things. The problem is that no one
have a time to investigate it and work on it. :-(
---
Ken'ichi HANDA
address@hidden