In article <jwvhcfvdrod.fsf-monnier+emacs@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca> writes:

> > C-s $(D**(B $B"y(B $(D**(B $B"y(B $(D**(B $B"y(B C-g C-g C-g C-g ESC x r e p o TAB r
> Hmm... "$(D**(B $B"y(B" in latin-1 is "0xC3 0xB6" which is the utf-8 codes for $(D+S(B,
> so the C-h l output indicates your terminal sends utf-8 sequences and
> Emacs gets them fine, but if you say that instead of $(D+S(B you saw some $B"y(B,
> it may indicate that your keyboard-coding-system somehow is set to use
> latin-1 coding system rather than utf-8, or maybe the binary codes get
> treated as latin-1 by the unicode-charset.

It seems that something is broken in isearch-x.el (although
unicode merge didn't change it).  I'm now investigating.
But, perhaps, it's time to implement the decoding of
keyboard input by C.  After multi-tty merge, we have the
function tty_read_avail_input.  I think that is the right
place to do that decoding.

---
Kenichi Handa
handa@ni.aist.go.jp