Closed GoogleCodeExporter closed 9 years ago
I saw there is a
# TODO lookup UTF8
a few lines above, so this is probably a known issue. It is not a problem for
me,
since I am doing my own custom key->char mapping, and thus I'm not using text
events
at all. As a quick fix, I'll just use errors='replace' locally to get rid of
the
exception.
Original comment by euccas...@gmail.com
on 20 Sep 2007 at 3:31
Possibly has some relevance to issue 65.
Original comment by Alex.Hol...@gmail.com
on 20 Sep 2007 at 9:38
Whoops, misread the comment; has nothing to do with Windows or issue 65.
Original comment by Alex.Hol...@gmail.com
on 20 Sep 2007 at 12:27
Fixed in r1265. Can you please check this, as I am only guessing that the
returned
unicode string is correct for the keyboard layout I selected.
If the Xlib UTF8 extension is not present, non-ascii characters will be ignored
instead of crashing (though this extension should be prevalent these days; it's
been
around for 5 years).
Is there a reason besides this issue you are using your own input method?
i.e., is
there some functionality here pyglet is missing?
Original comment by Alex.Hol...@gmail.com
on 20 Sep 2007 at 2:25
Original issue reported on code.google.com by
euccas...@gmail.com
on 20 Sep 2007 at 3:19