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: Emacs, Chinese language environment, and Japanese fonts Date: Thu, 15 Sep 2005 11:34:47 +0900 Message-ID: References: <87psrb9xhj.fsf@pacem.orebokech.com> NNTP-Posting-Host: main.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 1126751854 17389 80.91.229.2 (15 Sep 2005 02:37:34 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 15 Sep 2005 02:37:34 +0000 (UTC) Cc: lidaobing@gmail.com, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Sep 15 04:37:32 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1EFjc5-0006y4-Q7 for ged-emacs-devel@m.gmane.org; Thu, 15 Sep 2005 04:36:38 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EFjc5-0004qq-6w for ged-emacs-devel@m.gmane.org; Wed, 14 Sep 2005 22:36:37 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EFjb7-0004b6-Qt for emacs-devel@gnu.org; Wed, 14 Sep 2005 22:35:38 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EFjb0-0004YC-I1 for emacs-devel@gnu.org; Wed, 14 Sep 2005 22:35:31 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EFjb0-0004Xs-C8 for emacs-devel@gnu.org; Wed, 14 Sep 2005 22:35:30 -0400 Original-Received: from [192.47.44.130] (helo=tsukuba.m17n.org) by monty-python.gnu.org with esmtp (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA:24) (Exim 4.34) id 1EFjaX-0005hY-KN for emacs-devel@gnu.org; Wed, 14 Sep 2005 22:35:02 -0400 Original-Received: from nfs.m17n.org (nfs.m17n.org [192.47.44.7]) by tsukuba.m17n.org (8.13.4/8.13.4/Debian-3) with ESMTP id j8F2YmiX021909; Thu, 15 Sep 2005 11:34:48 +0900 Original-Received: from etlken (etlken.m17n.org [192.47.44.125]) by nfs.m17n.org (8.13.4/8.13.4/Debian-3) with ESMTP id j8F2Ym3R010570; Thu, 15 Sep 2005 11:34:48 +0900 Original-Received: from handa by etlken with local (Exim 3.36 #1 (Debian)) id 1EFjaJ-0000GI-00; Thu, 15 Sep 2005 11:34:47 +0900 Original-To: Romain Francoise In-reply-to: <87psrb9xhj.fsf@pacem.orebokech.com> (message from Romain Francoise on Wed, 14 Sep 2005 22:59:36 +0200) User-Agent: SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/22.0.50 (i686-pc-linux-gnu) MULE/5.0 (SAKAKI) 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:42939 Archived-At: In article <87psrb9xhj.fsf@pacem.orebokech.com>, Romain Francoise writes: > I received a bug report from a Chinese user complaining that Emacs 22 > wants to use a Japanese font to display a character from the Chinese > alphabet, even if the language environment is set to something Chinese > (in this case, Chinese-GB). > My guess is that the character is identical in Chinese and Japanese > (kanji) alphabets and that Emacs just uses the "best fitting" font, > which isn't installed on this user's workstation. Apparently, > (list-charset-chars 'chinese-gb2312) correctly shows the character, but > the font isn't selected when displaying a regular buffer. > Is that a bug or a configuration problem? I'm not really knowledgeable > about this stuff, can someone enlighten me? > You can find more information here: > I've just read that thread. In any Chinese-XXX lang. env., if that character is (0x4A4A of GB2312) encoded in UTF-8, Emacs correctly decodes it into chinese-gb charset. So, my question is how he got that character in Emacs buffer. One possibility is that he cut&pasted it from the other application and that application sent that character encoded in compound-text while designating JISX0212. In that case, Emacs surely decodes it into japanese-jisx0212, but that is a correct behaviour. (setq x-select-request-type '(UTF8_STRING COMPOUND-TEXT)) forces Emacs to ask the other application to send a selection data in utf-8 if possible. So, this setting will work for him. --- Kenichi Handa handa@m17n.org