This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Title: No visual feedback when entering japanese Characters in Entry widget
Type: behavior Stage: resolved
Components: Tkinter Versions: Python 3.4
Status: closed Resolution: third party
Dependencies: Superseder:
Assigned To: Nosy List: ned.deily, rovf
Priority: normal Keywords:

Created on 2014-05-29 14:51 by rovf, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Messages (2)
msg219347 - (view) Author: (rovf) Date: 2014-05-29 14:51
When I enter Japanese text in a tkinter entry widget, I don't get any visual feedback while typing; in particular, I don't get the Kanji selection box of the Kotaeri input method, which makes it impossible to choose the correct Kanji (try, for example, to type the words 合う, 会う and 遭う in a tkinter entry field). The only possibility is to enter the text in, say, a text editor and then copy them to the tkinter entry widget.

The error is specific to Mac OSX (at least to version 10.6). It does not occur on Windows.
msg219358 - (view) Author: Ned Deily (ned.deily) * (Python committer) Date: 2014-05-29 18:52
tkinter-based apps depend on the underlying Tk widget for text processing.  I know nothing about the various Japanese input methods on OS X but, in spot checking of a few, I observed no visual feedback with Katakana selected until I pressed the Return key, at which point all previously unechoed characters appeared.  I observed exactly the same behavior when using the Tk-supplied wish (/usr/local/bin/wish8.5 or 8.6) shell text demo.  (This was using the most recent ActiveTcl 8.5.15 and 8.6.1 releases.)  If you want to pursue the issue, I suggest checking the Tk project issue tracker and, if necessary, opening a new issue there with steps to reproduce using wish.
Date User Action Args
2022-04-11 14:58:04adminsetgithub: 65805
2014-05-29 18:52:02ned.deilysetstatus: open -> closed

nosy: + ned.deily
messages: + msg219358

resolution: third party
stage: resolved
2014-05-29 14:51:55rovfcreate