From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Kenichi Handa Newsgroups: gmane.emacs.devel Subject: Re: set-fontset-font and preferred charset? Date: Mon, 06 Jul 2009 21:17:41 +0900 Message-ID: References: <20090703.141522.801668491022750733.kasahara@nc.kyushu-u.ac.jp> <20090703.082403.252821682.wl@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1246882722 6980 80.91.229.12 (6 Jul 2009 12:18:42 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 6 Jul 2009 12:18:42 +0000 (UTC) Cc: kasahara@nc.kyushu-u.ac.jp, emacs-devel@gnu.org To: YAMAMOTO Mitsuharu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jul 06 14:18:34 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1MNn9W-0003N6-11 for ged-emacs-devel@m.gmane.org; Mon, 06 Jul 2009 14:18:34 +0200 Original-Received: from localhost ([127.0.0.1]:34691 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MNn9V-0001Rp-88 for ged-emacs-devel@m.gmane.org; Mon, 06 Jul 2009 08:18:33 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MNn8o-0001DA-2G for emacs-devel@gnu.org; Mon, 06 Jul 2009 08:17:50 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MNn8k-0001BE-2r for emacs-devel@gnu.org; Mon, 06 Jul 2009 08:17:49 -0400 Original-Received: from [199.232.76.173] (port=55752 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MNn8j-0001B8-K0 for emacs-devel@gnu.org; Mon, 06 Jul 2009 08:17:45 -0400 Original-Received: from mx1.aist.go.jp ([150.29.246.133]:48836) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MNn8i-0002gd-Sy for emacs-devel@gnu.org; Mon, 06 Jul 2009 08:17:45 -0400 Original-Received: from rqsmtp1.aist.go.jp (rqsmtp1.aist.go.jp [150.29.254.115]) by mx1.aist.go.jp with ESMTP id n66CHfh0016187; Mon, 6 Jul 2009 21:17:42 +0900 (JST) env-from (handa@m17n.org) Original-Received: from smtp3.aist.go.jp by rqsmtp1.aist.go.jp with ESMTP id n66CHfpb011141; Mon, 6 Jul 2009 21:17:41 +0900 (JST) env-from (handa@m17n.org) Original-Received: by smtp3.aist.go.jp with ESMTP id n66CHf3P017077; Mon, 6 Jul 2009 21:17:41 +0900 (JST) env-from (handa@m17n.org) Original-Received: from handa by etlken with local (Exim 4.69) (envelope-from ) id 1MNn8f-0004da-35; Mon, 06 Jul 2009 21:17:41 +0900 In-Reply-To: (message from YAMAMOTO Mitsuharu on Fri, 03 Jul 2009 17:09:43 +0900) X-detected-operating-system: by monty-python.gnu.org: Solaris 9 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:112075 Archived-At: In article , YAMAMOTO Mitsuharu writes: >>>>>> On Fri, 03 Jul 2009 16:21:40 +0900, Kenichi Handa said: > > So, if he uses 23.2 trunk code, there's no need of extra setting. > > Perhaps, I should add that code for 23.1 too because it can be > > considered as a bug that Emacs 23.1 dislays several characters as > > half width by M-x list-charset-chars RET japanese-jisx0208 RET. > I'm not sure if it is an intended behavior or a bug, but even with the > trunk code, M-x list-charset-chars RET japanese-jisx0208 RET shows > latin-1 characters such as PLUS-MINUS SIGN and MULTIPLICATION SIGN in > half width. Oops, I've overlooked that problem. Emacs searches for a font for C in this order: (1) search a font-group for C in the current fontset. (2) search a font-group for C in the default fontset. (3) search a fallback font-group of the current fontset. (4) search a fallback font-group of the default fontset. When a user specify a font (not fontset) as the default font, Emacs creates an fontset based on that font, and if the font is iso8859-1, the created fontset uses that font for iso-8859-1 characters. So, at the step (1) above, the default font is found for all iso-8859-1 characters although the preferable font should be found at the step (2). But, I'm now improving the font-searching routine for 23.2. One of the change I have in my mind is to merge the steps (1) and (2) (and (3) and (4)) while removing the duplicated font specifications. Once that is done, the above problem will be solved eventually. --- Kenichi Handa handa@m17n.org