[Python-bugs-list] [Bug #110671] Tk-based widgets misbehave with dead keys (PR#376)

[noreply@sourceforge.net]

Bug #110671, was updated on 2000-Jul-31 14:12
Here is a current snapshot of the bug.

Project: Python
Category: Tkinter
Status: Open
Resolution: None
Bug Group: 3rd Party
Priority: 5
Summary: Tk-based widgets misbehave with dead keys (PR#376)

Details: Jitterbug-Id: 376
Submitted-By: fstajano@uk.research.att.com
Date: Thu, 29 Jun 2000 12:49:44 -0400 (EDT)
Version: 1.6a2
OS: Windows 98 and 2000


This is a problem of the underlying widget set and not of Idle itself, but Idle
is where I encountered it (I normally use Emacs), and since Python 1.6 is the
unicode version I suppose it's worth looking into anyway (what good is it to
have international chars if you can't input them ;-)).

If, on Windows, you use a keyboard layout with dead keys, such as "United States
- International", then Idle does not respond properly to dead keys. In
particular, double-quote comes out as single-quote; single-quote comes out as
space; and accented characters come out as non-accented.

The lack of support for the accented chars is a minor nuisance, but the problems
with quotes are a major one -- Idle is almost unusable under these
circumstances. Not as bad as Pythonwin, though, which just crashes.

[As you will know, the US-I keyboard defines things like single-quote and
double-quote as dead keys so that one can produce accents and umlauts
respectively by following the dead key with the appropriate vowel. To produce a
double-quote on its own, you have to press double-quote followed by space.]



====================================================================
Audit trail:
Tue Jul 11 08:24:21 2000	guido	moved from incoming to open

Follow-Ups:

Date: 2000-Aug-28 00:37
By: effbot

Comment:
This is supposed to be fixed in Tk 8.3 and later; from the 8.3.0 changes document:

2000-02-08 (bug fix) fixed incorrect handling of CapsLock on Win9* and the use of dead keys on international keyboards (spjuth)

(haven't verified it yet, since 1.6's Tkinter causes my Win95 box to crash, no matter what Tk version I'm using)
-------------------------------------------------------

Date: 2000-Sep-19 10:19
By: loewis

Comment:
I can confirm that the problem occurs with 1.6a2 but is fixed in 2.0b1; likely due to the more recent Tk version.
-------------------------------------------------------

For detailed info, follow this link:
http://sourceforge.net/bugs/?func=detailbug&bug_id=110671&group_id=5470