From: Stefan Monnier <monnier@iro.umontreal.ca>
To: lconrad@laymusic.org
Cc: 1003@emacsbugs.donarmstrong.com
Subject: bug#1003: 23.0.60; set-keyboard-coding-system incompatible with TeX input method
Date: Sat, 20 Sep 2008 16:45:41 -0400 [thread overview]
Message-ID: <jwvbpyi5zcs.fsf-monnier+emacsbugreports@gnu.org> (raw)
In-Reply-To: <20080919161117.DE08EE3CD9A@clavichord> (Laura Conrad's message of "Fri, 19 Sep 2008 12:11:17 -0400 (EDT)")
> in TeX input mode, I expect to be able to type ént by typing "\'ent".
> When I set:
> (set-keyboard-coding-system 'utf-8)
> typing those four characters gives me some Chinese character.
IIUC the problem is that the input method processing is done before the
keyboard-coding-system processing. So the sequence "\ ' e n t" is
turned by the input method into "é n t" (i.e. 233 110 116) which is then
interpreted as a utf-8 sequence which happens to give you
a chinese character.
In Emacs-22, bytes such as 233 were different from any other char, so
such confusion wasn't possible, which worked around the underlying
ordering problem.
A real fix would probably be to perform keyboard-coding-system decoding
earlier, but it's a non trivial change which may introduce its own set
of problems.
Maybe another way to fix the problem is to let quail emit not just é but
the sequence [im-char é] and then have input-decode-map strip the
`im-char' pseudo event; this would protect those im-generated chars from
being processed by the keyboard-coding-system processing.
Handa?
Stefan
next prev parent reply other threads:[~2008-09-20 20:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-19 16:11 bug#1003: 23.0.60; set-keyboard-coding-system incompatible with TeX input method Unknown
2008-09-20 20:45 ` Stefan Monnier [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-05-25 4:44 Kenichi Handa
2009-05-25 11:01 ` Laura Conrad
[not found] ` <jwv1vqd47n7.fsf-monnier+emacsbugreports@gnu.org>
2009-07-01 11:49 ` Kenichi 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvbpyi5zcs.fsf-monnier+emacsbugreports@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=1003@emacsbugs.donarmstrong.com \
--cc=lconrad@laymusic.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.