unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Dorn <mail@muflax.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>, 17412@debbugs.gnu.org
Subject: bug#17412: 24.3; Unicode key events broken, not usable in input method
Date: Tue, 6 May 2014 19:38:24 +0100	[thread overview]
Message-ID: <CAEOcM3m_mPAMGz-MEaLfJ7K4n8FbSkwvnk3GFrquMS9OS-tAzQ@mail.gmail.com> (raw)
In-Reply-To: <jwviopiki5k.fsf-monnier+emacsbugs@gnu.org>

>> Digging around in keyboard.c, I found that read_char() only passes
>> events with keycode < 256 (line 3050ff) to input-method-function:
>
> Indeed, this has been in the input-method design from the start.
> I'd be interested to know why.  Handa?

I write a lot of linguistic analysis, and so added common IPA symbols
to my core keyboard layout, like ß, ł or æ. (I could type them through
an input method, but that would be slower and force me to use a
different typing method inside and outside of Emacs, which would slow
me down a lot.)

I recently set up a Cyrillic input method, but was surprised I
arbitrarily could use ß in quail but not ł, just because ß is below
the magic threshold. Unfortunately, merely turning off the conditional
in read_char() is not enough to get it to work.

More importantly, I also have most combining diacritic characters
(U+0301 ff) on keys and use them a lot. Switching them to some
"similar looking punctuation -> diacritic" input method would be
seriously annoying due to lots of conflicts (quoting a letter vs
umlauting it etc).

Most search features in Emacs don't do Unicode normalization, so ä (a
with umlaut) and ä (a with combining diacritic umlaut) don't match. I
added some normalization hacks to isearch and just force-normalize the
buffer when I save it, but wanted a more universal and clean solution.

I thought I could just set up a "letter + combining diacritic" ->
"normalized character" input method to fix most of this, but again
arbitrarily can't use any of the diacritics in quail.

>> [322] as key event seems strange to me. The XLib keycode for "ł" (as
>> reported by xev) is 0x1000142. Maybe Emacs cuts off the leading bit?
>
> 322 = U+0142, so it's really not strange at all: Emacs uses
> Unicode internally.

Ah, cool.





  reply	other threads:[~2014-05-06 18:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-05 22:29 bug#17412: 24.3; Unicode key events broken, not usable in input method Stefan Dorn
2014-05-06 16:06 ` Stefan Monnier
2014-05-06 18:38   ` Stefan Dorn [this message]
2014-05-06 18:55     ` Eli Zaretskii
2014-05-06 20:12       ` Stefan Monnier
2014-05-06 20:14         ` Daniel Colascione
2014-05-07 18:13         ` Eli Zaretskii
2014-05-12 23:23   ` K. Handa
2014-05-13  1:17     ` Stefan Monnier
2014-05-13 12:11       ` K. Handa

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=CAEOcM3m_mPAMGz-MEaLfJ7K4n8FbSkwvnk3GFrquMS9OS-tAzQ@mail.gmail.com \
    --to=mail@muflax.com \
    --cc=17412@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).