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: char-displayable-p issue Date: Wed, 22 Oct 2003 14:51:06 +0900 (JST) Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <200310220551.OAA07920@etlken.m17n.org> References: <20031021232240.14826.qmail@web60306.mail.yahoo.com> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII X-Trace: sea.gmane.org 1066802074 837 80.91.224.253 (22 Oct 2003 05:54:34 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 22 Oct 2003 05:54:34 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Wed Oct 22 07:54:31 2003 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1ACBx1-0008Li-00 for ; Wed, 22 Oct 2003 07:54:31 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1ACBx1-0002NK-00 for ; Wed, 22 Oct 2003 07:54:31 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.24) id 1ACBuP-00015p-K8 for emacs-devel@quimby.gnus.org; Wed, 22 Oct 2003 01:51:49 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24) id 1ACBuL-00015U-3Z for emacs-devel@gnu.org; Wed, 22 Oct 2003 01:51:45 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24) id 1ACBtp-00012a-D1 for emacs-devel@gnu.org; Wed, 22 Oct 2003 01:51:44 -0400 Original-Received: from [192.47.44.130] (helo=tsukuba.m17n.org) by monty-python.gnu.org with esmtp (Exim 4.24) id 1ACBto-00012X-OW for emacs-devel@gnu.org; Wed, 22 Oct 2003 01:51:12 -0400 Original-Received: from fs.m17n.org (fs.m17n.org [192.47.44.2]) by tsukuba.m17n.org (8.11.6p2/3.7W-20010518204228) with ESMTP id h9M5p7h02553; Wed, 22 Oct 2003 14:51:07 +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.6/3.7W-20010823150639) with ESMTP id h9M5p7s24293; Wed, 22 Oct 2003 14:51:07 +0900 (JST) Original-Received: (from handa@localhost) by etlken.m17n.org (8.8.8+Sun/3.7W-2001040620) id OAA07920; Wed, 22 Oct 2003 14:51:06 +0900 (JST) Original-To: mmaug@yahoo.com In-reply-to: <20031021232240.14826.qmail@web60306.mail.yahoo.com> (message from Michael Mauger on Tue, 21 Oct 2003 16:22:40 -0700 (PDT)) User-Agent: SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/21.3 (sparc-sun-solaris2.6) MULE/5.0 (SAKAKI) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:17314 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:17314 In article <20031021232240.14826.qmail@web60306.mail.yahoo.com>, Michael Mauger writes: > [1 ] > [1.1 ] > I can't reproduce that bug. When I turned on ruler-mode, I > see both characters in the ruler head. Isn't it a bug > specific to Windows? > Yes, it seems the problem is specific to Windows. Work > well on my GNU/Linux box. > I'm not sure that this is just a Windows issue -- it may > affect some X implementations as well. The problem seems > to be that the wildcard pattern generated in > `char-displayable-p' is not matching multiple hyphen > separated portions of the font name. That is, > '-*-*-iso8859-1' doesn't match any fonts while > '-*-*-*-*-*-*-*-*-*-*-*-*-iso8859-1' does. > Here's a patch that corrects the problem (and should work > reliably on all X implementations) but which runs very > slowly on Windows. Ummm, I didn't know that such a server exists. How about '-*-iso8859-1'? Doest it match all iso8859-1 fonts? If so, instead of just changing "-*-" to "-*-*-*-*-*-*-*-*-*-*-*-", generating the most compact font-pattern (i.e. no succeeding wildcards) will solve the problem without making Windows version slow. Could you try that? Even if that doesn't work, your patch is not enough. I think we must change the length of "-*-..-*-" according to the form of car of font-pattern ("FOUNDRY-FAMILY", "*FAMILY", or "FOUNDRY*") --- Ken'ichi HANDA handa@m17n.org