unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Kenichi Handa <handa@m17n.org>
Cc: monnier+gnu.emacs.help/news/@rum.cs.yale.edu,
	emacs-devel@gnu.org, ilya@Math.Berkeley.EDU
Subject: Re: MULE shows gibberish; now what?
Date: Thu, 10 Oct 2002 10:51:02 +0900 (JST)	[thread overview]
Message-ID: <200210100151.KAA19779@etlken.m17n.org> (raw)
In-Reply-To: <200210100055.g9A0tQg04263@rum.cs.yale.edu> (monnier+gnu/emacs@rum.cs.yale.edu)

In article <200210100055.g9A0tQg04263@rum.cs.yale.edu>, "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu> 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
handa@m17n.org

  reply	other threads:[~2002-10-10  1:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <amot9n$24j8$1@agate.berkeley.edu>
     [not found] ` <ao0hgi$1fim$1@agate.berkeley.edu>
2002-10-09 18:20   ` MULE shows gibberish; now what? Stefan Monnier <foo@acm.com>
2002-10-09 20:03     ` Ilya Zakharevich
2002-10-09 21:39       ` Stefan Monnier
2002-10-10  0:55         ` Ilya Zakharevich
2002-10-10  0:29     ` Kenichi Handa
2002-10-10  0:55       ` Stefan Monnier
2002-10-10  1:51         ` Kenichi Handa [this message]
2002-10-10  0:58       ` Ilya Zakharevich
2002-10-10  1:30         ` Kenichi Handa
2002-10-10  1:08       ` Ilya Zakharevich
2002-10-10  2:02         ` Kenichi Handa
2002-10-10  6:44           ` Ilya Zakharevich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200210100151.KAA19779@etlken.m17n.org \
    --to=handa@m17n.org \
    --cc=emacs-devel@gnu.org \
    --cc=ilya@Math.Berkeley.EDU \
    --cc=monnier+gnu.emacs.help/news/@rum.cs.yale.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).