[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 11:02:18 +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>, Ilya Zakharevich <address@hidden> writes:
>>  Then, if such a font can be distinguished from correct
>>  iso8859-5 fonts (perhaps, by family or foundary fields), the
>>  easiest solution is to ignore such a font by setting the
>>  variable `face-ignored-fonts' properly.

> It is not clear what "properly" means.

>  (setq face-ignored-fonts '(".*RAWIN-R"))

> does not fix the things;

>   (setq face-ignored-fonts '(".*Cronyx.*"))

> does fix the things...  The problematic font is

>  cyrillic-iso8859-5   -*-*-*-iso8859-5
>      [-Cronyx-Fixed-Medium-R-Normal--15-140-75-75-C-90-RAWIN-R]

Ok, then, I guess the original font name is:
and the alias name is

  (setq face-ignored-fonts '(".*RAWIN-R"))
can't reject the alias name but
  (setq face-ignored-fonts '(".*Cronyx.*"))

The reason why M-x describe-fontset shows the original font
name is that Emacs calls XLoadQueryFont to get also the info
once a font is decided.  Then Emacs extracts "FONT" property
(if any) from the info and remember it as the correct font

>>  > It could also look at the CHARSET_REGISTRY and CHARSET_ENCODING property
>>  > of the font (rather than assuming it's the same as in the fontname) ?
>>  To get those properties, we must call XListFontsWithInfo
>>  which, I think, is very slow compared with XListFonts.

> Hmm, is it possible to get the actual font name without getting the info?

No, as far as I know.

Ken'ichi HANDA

reply via email to

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