From: Kenichi Handa <handa@m17n.org>
Cc: ibr@radix50.net, emacs-devel@gnu.org
Subject: Re: ping2: Re: <Cyrillic_schwa> is undefined
Date: Mon, 24 Oct 2005 20:29:00 +0900 [thread overview]
Message-ID: <E1EU0Vg-0004aM-00@etlken> (raw)
In-Reply-To: <E1ET8Rq-0001LA-00@etlken> (message from Kenichi Handa on Sat, 22 Oct 2005 10:45:26 +0900)
In article <E1ET8Rq-0001LA-00@etlken>, Kenichi Handa <handa@m17n.org> writes:
> In article <20051021180026.GA19632@radix50.net>, Baurzhan Ismagulov <ibr@radix50.net> writes:
>> Hello Handa,
>> On Wed, Oct 05, 2005 at 09:53:48PM +0900, Kenichi Handa wrote:
>>> But, for instance, for XK_Cyrillic_GHE_bar, I don't know the
>>> corresponding Unicode character code. If you give me a list
>>> of keysym_codes and the corresponding Unicode character
>>> code, I'll add it in x-win.el.
>> could you please share your plans regarding this issue? The list of the
>> characters and a patch are at
>> http://lists.gnu.org/archive/html/emacs-devel/2005-10/msg00176.html .
>> The patch may be encoded wrongly.
> I'm very sorry for not responding on this matter. I'm now
> working on it. Please wait for a while.
I've just installed a fix. Actually, I registered more
Cyrillic characters in x-keysym-table than what you listed
(e.g. 0x681 for XK_Cyrillic_ZHE_descender) because...
James Cloos <cloos@jhcloos.com> writes:
[...]
> The diff between revisions 1.2 and 1.3 of that file as seen at:
> http://cvs.freedesktop.org/xorg/xc/include/keysymdef.h?r1=1.2&r2=1.3
> shows several changes from old-style keysyms to unicode keysyms.
the above page indicates that some version of X contains
them too, and I confirmed that some distribution surely has
them.
In addition,
> That checkin replaced all uppercase hex constants with lowercase,
> added unicode codepoint comments (from UnicodeData.txt), and
> switched several blocks to the unicode block (0x1000000 to 0x1FFFFFF).
I installed changes to handle them in xterm.c without
calling Lisp but by directly using MAKE_CHAR macro.
But, I can't test them becasue my X server doesn't have
those keysyms. If yours does, please test it.
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2005-10-24 11:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-01 19:31 <Cyrillic_schwa> is undefined Baurzhan Ismagulov
2005-10-05 12:53 ` Kenichi Handa
2005-10-05 18:46 ` James Cloos
2005-10-05 19:25 ` Stefan Monnier
2005-10-06 2:04 ` Kenichi Handa
2005-10-06 16:35 ` James Cloos
2005-10-06 17:58 ` James Cloos
2005-10-05 21:49 ` Baurzhan Ismagulov
2005-10-12 18:48 ` ping: " Baurzhan Ismagulov
2005-10-21 18:00 ` ping2: " Baurzhan Ismagulov
2005-10-22 1:45 ` Kenichi Handa
2005-10-22 7:25 ` Baurzhan Ismagulov
2005-10-24 11:29 ` Kenichi Handa [this message]
2005-10-25 19:00 ` Baurzhan Ismagulov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1EU0Vg-0004aM-00@etlken \
--to=handa@m17n.org \
--cc=emacs-devel@gnu.org \
--cc=ibr@radix50.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).