[Python-bugs-list] [Bug #113795] IDLE 0.6 with Python 2.0b1 doesn't handle chinese characters

noreply@sourceforge.net noreply@sourceforge.net
Wed, 20 Sep 2000 18:01:35 -0700


Bug #113795, was updated on 2000-Sep-07 06:49
Here is a current snapshot of the bug.

Project: Python
Category: Tkinter
Status: Open
Resolution: Later
Bug Group: 3rd Party
Priority: 1
Summary: IDLE 0.6 with Python 2.0b1 doesn't handle chinese characters

Details: I just switched from 1.5.2 to 2.0b1 on W2K/Simplified Chinese version. I used to be able to input chinese characters directly into IDLE, and access violations did happen quite often. Now with 2.0b1, I can't even input chinese characters into the IDLE window anymore:IDLE automatically changed chinese characters into illegible stuff; it's the same when I copy from a text editor and paste into the IDLE window. I guess it's related to the induction of unicode support in 2.0, but is there a workaround I should know, or I should switch back to 1.5.2, or it's a bug worth fixing?

Thanks.


Follow-Ups:

Date: 2000-Sep-07 15:06
By: jhylton

Comment:
Please do triage on this bug.
-------------------------------------------------------

Date: 2000-Sep-14 23:13
By: tim_one

Comment:
Assigned to Fredrik, because Swedes have an uncanny intuition about how IDLE and Tk work in the presence of characters I can't get at <0.9 wink>.  Boosted the priority because it sounds like a legit practical problem.
-------------------------------------------------------

Date: 2000-Sep-20 12:47
By: loewis

Comment:
I can reproduce the problem by installing a Russion or Arabic keyboard layout on Win2k; typing into an Entry or Text widget displays Latin-1 characters. I can observe the same problem with a plain 8.3 wish, so it appears to be a bug in Tk - which apparently truncates characters on input. So I propose to close this as 3rd Party/Later, and recategorize it as Tkinter.
-------------------------------------------------------

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