Message76164
I suceeded to reproduce this issue with coLinux + UltraVNC on Win2000.
Yes, py3k claimed utf-8 error, so I tried trunk. Here is result.
*** event.keycode: 8
*** event.state: 0
*** event.char: ''
*** event.keycode: 16
*** event.state: 4
*** event.char: '\xc0\x80'
This '\xc0\x80' seems to be used in tcl as null byte '\0'. You can see
this magic value in tcl source and google.
I think we should convert this to '\x00' at python side. (shouldn't
treat this as utf-16)
I can see py3k + adhok.patch can output this result.
*** event.keycode: 8
*** event.state: 0
*** event.char: ''
*** event.keycode: 16
*** event.state: 4
*** event.char: '\x00'
Probably Tcl_GetUnicode does this conversion inside. (I'm not sure,
because I didn't look into source code so deeply) And I'm not sure why
this error doesn't happen with tk8.5. |
|
Date |
User |
Action |
Args |
2008-11-21 08:19:12 | ocean-city | set | recipients:
+ ocean-city, nnorwitz, kbk, gpolo |
2008-11-21 08:19:12 | ocean-city | set | messageid: <1227255552.37.0.943052959597.issue1028@psf.upfronthosting.co.za> |
2008-11-21 08:19:11 | ocean-city | link | issue1028 messages |
2008-11-21 08:19:10 | ocean-city | create | |
|