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: find-composition still depends on the composition property Date: Mon, 20 Oct 2008 15:46:37 +0900 Message-ID: References: <87tzbh7kd9.fsf@jurta.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1224510943 13685 80.91.229.12 (20 Oct 2008 13:55:43 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 20 Oct 2008 13:55:43 +0000 (UTC) Cc: lekktu@gmail.com, emacs-devel@gnu.org To: Juri Linkov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Oct 20 15:56:48 2008 connect(): Connection refused 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 1KroYb-00067z-VW for ged-emacs-devel@m.gmane.org; Mon, 20 Oct 2008 08:48:02 +0200 Original-Received: from localhost ([127.0.0.1]:36857 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KroXW-0008DP-LZ for ged-emacs-devel@m.gmane.org; Mon, 20 Oct 2008 02:46:54 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KroXS-0008Cz-TP for emacs-devel@gnu.org; Mon, 20 Oct 2008 02:46:50 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KroXR-0008CV-Tj for emacs-devel@gnu.org; Mon, 20 Oct 2008 02:46:50 -0400 Original-Received: from [199.232.76.173] (port=60305 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KroXR-0008CL-Ol for emacs-devel@gnu.org; Mon, 20 Oct 2008 02:46:49 -0400 Original-Received: from mx20.gnu.org ([199.232.41.8]:4306) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1KroXR-0000pf-9B for emacs-devel@gnu.org; Mon, 20 Oct 2008 02:46:49 -0400 Original-Received: from mx1.aist.go.jp ([150.29.246.133]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KroXN-00051I-A7 for emacs-devel@gnu.org; Mon, 20 Oct 2008 02:46:45 -0400 Original-Received: from rqsmtp2.aist.go.jp (rqsmtp2.aist.go.jp [150.29.254.123]) by mx1.aist.go.jp with ESMTP id m9K6kbQQ014417; Mon, 20 Oct 2008 15:46:37 +0900 (JST) env-from (handa@m17n.org) Original-Received: from smtp4.aist.go.jp by rqsmtp2.aist.go.jp with ESMTP id m9K6kbSM024992; Mon, 20 Oct 2008 15:46:37 +0900 (JST) env-from (handa@m17n.org) Original-Received: by smtp4.aist.go.jp with ESMTP id m9K6kbsQ015734; Mon, 20 Oct 2008 15:46:37 +0900 (JST) env-from (handa@m17n.org) Original-Received: from handa by etlken.m17n.org with local (Exim 4.69) (envelope-from ) id 1KroXF-0005mK-07; Mon, 20 Oct 2008 15:46:37 +0900 In-reply-to: <87tzbh7kd9.fsf@jurta.org> (message from Juri Linkov on Mon, 20 Oct 2008 02:15:17 +0300) X-MIME-Autoconverted: from 8bit to quoted-printable by mx1.aist.go.jp id m9K6kbQQ014417 X-detected-kernel: by mx20.gnu.org: Solaris 9 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6, seldom 2.4 (older, 4) 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:104664 Archived-At: In article <87tzbh7kd9.fsf@jurta.org>, Juri Linkov write= s: > What do you think about displaying the Unicode information of the > combining character too? > Currently there is no easy way to display the information (name, catego= ry) > about the combining character because the user can't put point on the > combining character and type `C-u C-x =3D'. When you type C-u C-x =3D on a composed characters, Emacs displays how it is composed. For instance, when a buffer contains the sequence "a" "U+300" "U+316" composed into one glyph, and you type C-u C-x =3D on it, Emacs shows something like this information. [...] Composed with the following character(s) "=CC=81=CC=96" using this font: ^^^^ xft:-Misc-Fixed-normal-normal-normal-*-20-*-*-*-c-*-iso10646-1 by these glyphs: [...] As each character ocupies one column in the part "=CC=81=CC=96", you can easily put cursor on any of a character and type C-u C-x =3D. Isn't it good enough? --- Kenichi Handa handa@ni.aist.go.jp