[issue22408] Tkinter doesn't handle Unicode dead key combinations on Windows
Changes by irdb dalba.w...@gmail.com: -- nosy: +irdb ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22408 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22408] Tkinter doesn't handle Unicode dead key combinations on Windows
Drekin added the comment: I installed wish and tried the demos shipped with Python. The behavior occurs during the demo basic editable text. So it's an issue of Tk itself. Actually the same behavior occurs even in the wish shell. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22408 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22408] Tkinter doesn't handle Unicode dead key combinations on Windows
Ned Deily added the comment: OK, then if you want to pursue the issue, I'd suggest asking on one of the Tcl/Tk forums (perhaps comp.lang.tcl) or Stackoverflow and/or checking the Tk issue tracker (https://core.tcl.tk/tk/reportlist). Good luck! -- resolution: - third party stage: - resolved status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22408 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22408] Tkinter doesn't handle Unicode dead key combinations on Windows
Drekin added the comment:
By modifier I mean a key like Shift, Ctrl, Alt, AltGr; or the corresponding
modifier state. A combination modifier + base key produces either special
action or a character or a dead key. A dead key affects the next character
rather than producing a character itself. Dead keys can be even chained, i.e. a
sequence [previous dead key, modifier + base key] can produce another dead key.
(Aside: This feature has been present on Windows for long time, but is used
very rarely and applications are buggy. I spent some time designing my Unicode
keyboard layout using chained dead keys to produce various mathematical
symbols. Then I found out than some applications have problems with the feature
– including Firefox. It's basically because they try to implement the
interpretation of keyboard layout by themselves rather then using standard
Windows implementation through API.)
For example standard Czech keyboard use the AltGr key and the corresponing
state to produce characters like $, #, , @, {, }, [, ], because the top row is
used for common diacritical combinations and its Shift state for numbers. I
understand that English doesn't need many characters and so the layout usually
doesn't need AltGr or dead keys. But I think even English keyboard should be
able to type characters like English quotes, N-dash, or ellipsis: “, ”, –, ….
I have also changed the title.
--
title: Tkinter doesn't handle Unicode key events on Windows - Tkinter doesn't
handle Unicode dead key combinations on Windows
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22408
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22408] Tkinter doesn't handle Unicode dead key combinations on Windows
Ned Deily added the comment: I guess it still comes down to whether this is an issue in tkinter or in Tk itself. Almost all character processing and event generation is done in Tk. One way to isolate the issue would be to use text widgets in the Tk wish shell and its demo programs. They should be available in the ActiveState ActiveTcl distribution. (I'm assuming that the Python Windows installer does not include wish but I don't know that for a fact.) -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue22408 ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
