From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Kenichi Handa Newsgroups: gmane.emacs.devel Subject: Re: MULE shows gibberish; now what? Date: Thu, 10 Oct 2002 11:02:18 +0900 (JST) Sender: emacs-devel-admin@gnu.org Message-ID: <200210100202.LAA19794@etlken.m17n.org> References: <5lu1jvfp9c.fsf@rum.cs.yale.edu> <200210100029.JAA19642@etlken.m17n.org> <20021010010840.GD3346@math.berkeley.edu> NNTP-Posting-Host: localhost.gmane.org Mime-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII X-Trace: main.gmane.org 1034215684 8227 127.0.0.1 (10 Oct 2002 02:08:04 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Thu, 10 Oct 2002 02:08:04 +0000 (UTC) Cc: monnier+gnu.emacs.help/news/@rum.cs.yale.edu, emacs-devel@gnu.org Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 17zSk5-000286-00 for ; Thu, 10 Oct 2002 04:08:01 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 17zTYO-0001iS-00 for ; Thu, 10 Oct 2002 05:00:00 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.10) id 17zSiF-0003sY-00; Wed, 09 Oct 2002 22:06:07 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10) id 17zShF-0003aT-00 for emacs-devel@gnu.org; Wed, 09 Oct 2002 22:05:05 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10) id 17zSem-0000ap-00 for emacs-devel@gnu.org; Wed, 09 Oct 2002 22:02:38 -0400 Original-Received: from tsukuba.m17n.org ([192.47.44.130]) by monty-python.gnu.org with esmtp (Exim 4.10) id 17zSeg-0000R1-00 for emacs-devel@gnu.org; Wed, 09 Oct 2002 22:02:27 -0400 Original-Received: from fs.m17n.org (fs.m17n.org [192.47.44.2]) by tsukuba.m17n.org (8.11.6/3.7W-20010518204228) with ESMTP id g9A22JF05988; Thu, 10 Oct 2002 11:02:19 +0900 (JST) (envelope-from handa@m17n.org) Original-Received: from etlken.m17n.org (etlken.m17n.org [192.47.44.125]) by fs.m17n.org (8.11.3/3.7W-20010823150639) with ESMTP id g9A22IR23511; Thu, 10 Oct 2002 11:02:18 +0900 (JST) Original-Received: (from handa@localhost) by etlken.m17n.org (8.8.8+Sun/3.7W-2001040620) id LAA19794; Thu, 10 Oct 2002 11:02:18 +0900 (JST) Original-To: ilya@Math.Berkeley.EDU In-reply-to: <20021010010840.GD3346@math.berkeley.edu> (message from Ilya Zakharevich on Wed, 9 Oct 2002 18:08:41 -0700) 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) Errors-To: emacs-devel-admin@gnu.org X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.0.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.emacs.devel:8497 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:8497 In article <20021010010840.GD3346@math.berkeley.edu>, Ilya Zakharevich 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: -Cronyx-Fixed-Medium-R-Normal--15-140-75-75-C-90-RAWIN-R and the alias name is -Cronyx-Fixed-Medium-R-Normal--15-140-75-75-C-90-ISO8859-5 Thus, (setq face-ignored-fonts '(".*RAWIN-R")) can't reject the alias name but (setq face-ignored-fonts '(".*Cronyx.*")) can. 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 name. >> > 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 handa@m17n.org