New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IDLE does not work with Unicode #48902
Comments
I have installed python 3.0 on Ubuntu 8.10 yesterday and played around The terminal works fine. It lets me input Japanese and runs commands So I used gedit and saved a simple print("Hello(in Japanese chars)"), (Can I also make sure that I'm opening IDLE correctly? This is how I do it:
1)Open Terminal
2)~$ Python.3.0
3)>>> input idlelib.idle Thank You in advance. |
I can't seem to reproduce that, maybe it could be a tk issue ? Can you try writing anything (that doesn't work on IDLE) on a from tkinter import Text
text = Text()
print(text.tk.call('info', 'patchlevel'))
text.focus_set()
text.pack()
text.mainloop() |
I've installed Python 3.1.1 on OSX today.
1) When I use the Japanese input from OSX, IDLE interprets any character
I attempt to type as a space.
2) When I paste a Japanese string from a different place, it is
correctly handled. For ex:
>>> print('ここ')
ここ
>>>
While on Python 2.5's IDLE I had:
>>> print('ここ')
Unsupported characters in input
by default. In any case, IDLE 3.1.1 does not respect the input source and that makes Note: IDLE respect OSX dead keys and I can correctly use "Alt+c" to |
I opened my IDLE (v. 3.2.2 windows xp) and pasted in |
alt-c does nothing for me |
For now unicode BMP has full support in TK while non-BMP characters doesn't works. 'こ' character is BMP symbol:
>>> hex(ord('こ'))
'0x3053'
which is lesser than non-BMP space (starting from 0x10000). I have no idea why alt-c doesn't converted to 'ç' (also BMP by the way) and why it has been processed by Helary's IDLE. I have no any Mac box nearby to check. |
I close this issue because:
See progress of bpo-14200 and others for non-BMP. |
I would say that alt-c is not a problem at all, but, some people might use 'ç' more that me, (I never have used 'ç' spesificaly) |
To add to the other comments, problems with input methods using Python 3 and Tkinter or IDLE are usually platform-specific issues with the implementation of Tk. In particular, the issue Jean-Christophe reported with Python 3.1.1 was very likely due to its use of the old Tk 8.4 (at least with the python.org installer). Current versions of Python 3.2.x for OS X 10.6+ link with the newer Tk 8.5, the very latest releases of which by ActiveState contain important fixes for input methods using composite characters (http://www.python.org/download/mac/tcltk/ has the most up-to-date information). Also, note to the original poster, you either made a typo in the bug report ("UFT-8" - it should be "UTF-8") or, if you actually tried that locale, it might explain why you had problems. If someone can reproduce a problem with a current Python 3.2.x or later, please re-open with details. |
Daniel Swanson, maybe my msg156512 was not obvious. See http://en.wikipedia.org/wiki/Mapping_of_Unicode_characters |
ok |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: