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: is undefined Date: Thu, 06 Oct 2005 11:04:48 +0900 Message-ID: References: <20051001193132.GE25392@radix50.net> 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 1128564415 3759 80.91.229.2 (6 Oct 2005 02:06:55 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 6 Oct 2005 02:06:55 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Oct 06 04:06:53 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1ENL85-0007uS-7o for ged-emacs-devel@m.gmane.org; Thu, 06 Oct 2005 04:05:05 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ENL84-0006JW-Ko for ged-emacs-devel@m.gmane.org; Wed, 05 Oct 2005 22:05:04 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1ENL7v-0006J8-T6 for emacs-devel@gnu.org; Wed, 05 Oct 2005 22:04:56 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1ENL7u-0006Ih-OZ for emacs-devel@gnu.org; Wed, 05 Oct 2005 22:04:55 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ENL7u-0006Ic-HB for emacs-devel@gnu.org; Wed, 05 Oct 2005 22:04:54 -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 1ENL7t-0002ly-VT for emacs-devel@gnu.org; Wed, 05 Oct 2005 22:04:54 -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 j9624pUi005895; Thu, 6 Oct 2005 11:04:51 +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 j9624nSu026285; Thu, 6 Oct 2005 11:04:51 +0900 Original-Received: from handa by etlken with local (Exim 3.36 #1 (Debian)) id 1ENL7o-0003li-00; Thu, 06 Oct 2005 11:04:48 +0900 Original-To: James Cloos In-reply-to: (message from James Cloos on Wed, 05 Oct 2005 14:46:53 -0400) 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:43597 Archived-At: In article , James Cloos writes: >>>>>> "Kenichi" == Kenichi Handa writes: Kenichi> It seems that these X11 keysyms (in Kenichi> /usr/include/X11/keysymdefs.h, perhaps newly added) are not Kenichi> registered in x-keysym-table (in lisp/term/x-win.el). > For the Cyrillic, see /usr/include/X11/keysymdef.h on a current > install, or online at: > http://cvs.freedesktop.org/xorg/xc/include/keysymdef.h?rev=1.3&view=markup > It has unicode values for each keysym that is in unicode. (And note > that for any keysym that matches (and 0x01000000 keysym) the unicode > codepoint can be found by (and 0xFFFFFF keysym). Thank you for the info, but, oops, it doesn't have these lines (they exist in my debian): #define XK_Cyrillic_GHE_bar 0x680 [...] #define XK_Cyrillic_u_macron 0x69f but have: #define XK_Cyrillic_GHE_bar 0x1000492 /* U+0492 CYRILLIC CAPITAL LETTER GHE WITH STROKE */ [...] #define XK_Cyrillic_u_macron 0x10004ef /* U+04EF CYRILLIC SMALL LETTER U WITH MACRON */ What's going on here? Anyway, as it's easy to handle them in emacs-unicode-2, I've just commited a code for that for emacs-unicode-2. > I'm seeing a similar problem with . > It works for every app other than Emacs. > I don't know whether it is a regression; I only tried it becuase > quail was broken in emacs-unicode-2 of a few days ago (since fixed). > I would be useful if X's standard compose feature were usable in > emacs. Or, OTOH, perhaps it would make a good alternate first > stroke for the quail methods like rfc1345, sqml, latex, etc. As I'm not European users, I don't know how Multi_key is used. Could you explain the detail of the current problem? --- Kenichi Handa handa@m17n.org