[I18n-sig] py1.6a2p1 IDLE annoyance
takeuchi
takeuchi.shohei@lab.ntt.co.jp
Tue, 11 Apr 2000 13:21:05 +0900
This is a multi-part message in MIME format.
------=_NextPart_000_0033_01BFA3B8.CAAFEBE0
Content-Type: text/plain;
charset="iso-2022-jp"
Content-Transfer-Encoding: 7bit
Hi folks,
Thank you Guido for updating IDLE shell string input features according to
my private mail.
I've just got your py1.6a2p1 from the site
and tried. I hate to say like this but
IDLE shell is worse than before.
Here is another my story.
IDLE shell now has a consistant behavior to command line shell
except appearance on Win98 !
While Input string is saved as a Proper native encoded string (Shift JIS ),
echo backed string looks broken on the screen.
So user can not see the griph at all !
On Py1.6a2p1 IDLE Shell with Win98 Japanese Edition
# When Type Japanese alphabet "$B$"(B"
>>> s = raw_input("Echo backed broken griph")
>>> s
'\202\240' # SHift JIS encoding for the input
>>> print s
$B""!!(B# A broken griph comes up
>>> u = unicode( s,"mbcs")
>>> u
u'\u3042' # UTF-8 encoding for s
>>>print u
$B$"!!!!!!(B # A proper griph comes up
Tk8.3 seems to handle only UTF-8 strings,
so I think IDLE have to go with them.
I hope IDLE allows to customize shell
encoding so that unicode object is created
automatically from key input.
Any Idea?
Best Regards,
Takeuchi
------=_NextPart_000_0033_01BFA3B8.CAAFEBE0
Content-Type: text/html;
charset="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-2022-jp">
<META content=3D"MSHTML 5.50.4030.2400" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3D"Courier New" size=3D2>Hi folks, </FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2></FONT> </DIV>
<DIV><FONT face=3D"Courier New" size=3D2>Thank you Guido for updating =
IDLE shell=20
string input features according to my private mail.</FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2></FONT> </DIV>
<DIV><FONT face=3D"Courier New" size=3D2>I've just got your py1.6a2p1 =
from the=20
site</FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2>and tried. I hate to say =
like this but=20
</FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2>IDLE shell is worse than=20
before.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3D"Courier New" size=3D2>Here is another my =
story.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>IDLE shell now has a =
consistant behavior=20
to command line shell</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>except appearance on Win98 =
!</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>While Input string is saved as a =
Proper native=20
encoded string (Shift JIS ), echo backed string looks broken on the =
screen.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>So user can =
not see the=20
griph at all ! </FONT></DIV>
<DIV><FONT face=3DCourier size=3D2></FONT> </DIV>
<DIV><FONT face=3DCourier size=3D2>On Py1.6a2p1 IDLE Shell with Win98=20
Japanese Edition </FONT></DIV>
<DIV><FONT face=3DCourier size=3D2># When Type Japanese alphabet =
"=1B$B$"=1B(B"=20
</FONT></DIV>
<DIV><FONT face=3DCourier size=3D2>>>> s =3D raw_input("Echo =
backed broken=20
griph") </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>>>> s</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>'\202\240' # SHift JIS encoding =
for the=20
input </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>>>> print s</FONT></DIV>
<DIV><FONT face=3DCourier size=3D2>=1B$B""!!=1B(B# A broken griph =
comes up</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>>>> u =3D =
unicode(</FONT> <FONT=20
face=3DArial size=3D2>s,"mbcs")</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>>>> u </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>u'\u3042' # UTF-8 encoding for =
s</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>>>>print u</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>=1B$B$"!!!!!!=1B(B # A proper griph =
comes up </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3D"Courier New" size=3D2>Tk8.3 seems to handle only =
UTF-8=20
strings,</FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2>so I think IDLE have to go =
with=20
them.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3D"Courier New" size=3D2>I hope IDLE allows to=20
customize shell </FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2>encoding so that unicode=20
object is created</FONT></DIV>
<DIV><FONT face=3D"Courier New" size=3D2>automatically from key =
input.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3D"Courier New" size=3D2>Any Idea?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3D"Courier New" size=3D2>Best Regards,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3D"Courier New" size=3D2>Takeuchi</FONT> </DIV>
<DIV><FONT face=3D"Courier New" =
size=3D2></FONT> </DIV></BODY></HTML>
------=_NextPart_000_0033_01BFA3B8.CAAFEBE0--