On Dec 12, 2007 6:30 PM, Stefan Monnier <monnier@iro.umontreal.ca> wrote:

> Hmm.. if you just remove this eassert, you should get back the previous
> behavior.  But then I wonder: is this previous behavior correct, and if
> so, why?

No idea.

> Basically, the issue is that when a key is pressed, the W32 code inserts
> a "ASCII_KEYSTROKE_EVENT" in the queue, even for non-ASCII chars, and
> then keyboard.c applies a "& 0377" to it, so there's a risk of losing
> some bits and turning a non-ASCII keypress into some ASCII char.

Without the eassert, C-ñ returns ' (U+2018, translated from \221), C-ç
returns ‡ (U+2021, translated from \207). Not sure whether that is
intended or not.

             Juanma