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: bug#613: 23.0.60; Unicode display problems Date: Thu, 21 Aug 2008 10:01:54 +0900 Message-ID: References: <87myjv2tc8.fsf@stupidchicken.com> <87zlnrx33y.fsf@physik.rwth-aachen.de> <87ej52vg8r.fsf@physik.rwth-aachen.de> <873al2sd2h.fsf@physik.rwth-aachen.de> <87od3qqvlg.fsf@physik.rwth-aachen.de> <87k5ebbrq1.fsf@physik.rwth-aachen.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII X-Trace: ger.gmane.org 1219280584 21291 80.91.229.12 (21 Aug 2008 01:03:04 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 21 Aug 2008 01:03:04 +0000 (UTC) Cc: sand@blarg.net, 613@emacsbugs.donarmstrong.com, emacs-devel@gnu.org To: Torsten Bronger Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Aug 21 03:03:56 2008 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 1KVyaZ-0001Ur-U0 for ged-emacs-devel@m.gmane.org; Thu, 21 Aug 2008 03:03:48 +0200 Original-Received: from localhost ([127.0.0.1]:39074 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KVyZc-0007D6-QX for ged-emacs-devel@m.gmane.org; Wed, 20 Aug 2008 21:02:48 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KVyZY-0007Ce-I3 for emacs-devel@gnu.org; Wed, 20 Aug 2008 21:02:44 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KVyZX-0007C5-Tz for emacs-devel@gnu.org; Wed, 20 Aug 2008 21:02:44 -0400 Original-Received: from [199.232.76.173] (port=49030 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KVyZX-0007C0-QX for emacs-devel@gnu.org; Wed, 20 Aug 2008 21:02:43 -0400 Original-Received: from mx1.aist.go.jp ([150.29.246.133]:61223) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KVyZV-0005tw-Sm for emacs-devel@gnu.org; Wed, 20 Aug 2008 21:02:42 -0400 Original-Received: from rqsmtp2.aist.go.jp (rqsmtp2.aist.go.jp [150.29.254.123]) by mx1.aist.go.jp with ESMTP id m7L1274f027459; Thu, 21 Aug 2008 10:02:07 +0900 (JST) env-from (handa@m17n.org) Original-Received: from smtp2.aist.go.jp by rqsmtp2.aist.go.jp with ESMTP id m7L127HN012411; Thu, 21 Aug 2008 10:02:07 +0900 (JST) env-from (handa@m17n.org) Original-Received: by smtp2.aist.go.jp with ESMTP id m7L11sY5026539; Thu, 21 Aug 2008 10:01:56 +0900 (JST) env-from (handa@m17n.org) Original-Received: from handa by etlken.m17n.org with local (Exim 4.69) (envelope-from ) id 1KVyYk-0002tv-9h; Thu, 21 Aug 2008 10:01:54 +0900 In-reply-to: <87k5ebbrq1.fsf@physik.rwth-aachen.de> (message from Torsten Bronger on Wed, 20 Aug 2008 18:01:42 +0200) User-Agent: SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/23.0.60 (i686-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) X-detected-kernel: 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:102747 Archived-At: In article <87k5ebbrq1.fsf@physik.rwth-aachen.de>, Torsten Bronger writes: > It works now as for this change but apparently, it still is not > fully correct. At least two characters that I use ("prime" #x2032 > and "cubic root" #x221b) are still too wide, however, I don't know > whether they are available in the DejaVu font. Dejavu Sans Mono doesn't have those characters. In such a case, it's very difficult to decide which is the "correct" font. A while ago, stephen@xemacs.org suggested to utilize fontconfig's language repertoires. I'm going to implement that somehow. When it is done, for non-CJK locale users, Emacs can select a single-width font. > Do you think it's sensible to create a file will all codepoints and > look for problematic chars in a systematic way? No, it won't help. --- Kenichi Handa handa@ni.aist.go.jp