[Top][All Lists]

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

Re: MULE shows gibberish; now what?

From: Ilya Zakharevich
Subject: Re: MULE shows gibberish; now what?
Date: Wed, 9 Oct 2002 17:58:19 -0700
User-agent: Mutt/1.4i

On Thu, Oct 10, 2002 at 09:29:12AM +0900, Kenichi Handa wrote:
> > 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.

> 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.

OK, if you do this, please put '-cronix-*' fonts there.  It is a
horrible thing what they did.

> > BTW, I agree that the fontset management could be made simpler (I think
> > it's not just a question of the doc being dense or incomplete).
> > Especially in your case, there should be some way to say something like:
> >    (fontset-prefer-font 'cyrillic-iso8859-5 "-etl-fixed-*-iso8859-5")
> Is that intention different from this?
> (dolist (fontset (fontest-list))
>   (set-fontset-font fontset 'cyrillic-iso8859-5
>                   '("etl-fixed" . "iso8859-5")))

Would not work if there is no etl-fixed fonts on the site?


reply via email to

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