Re: [IronPython] IronPython codec names not compatible with CPython

2006-10-09 Thread Dino Viehland
ink the main thing to capture here is that we're missing some names & alises in our standard encodings. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Machin Sent: Saturday, October 07, 2006 7:54 PM To: Discussion of IronPython Subj

Re: [IronPython] IronPython codec names not compatible with CPython

2006-10-08 Thread John Machin
On 8/10/2006 12:54 PM, John Machin wrote: > CPython recognises both 'gbk' and 'cp936' i.e. unicode('some string', > 'gbk') does what you'd expect. > IronPython 1.0.1 recognises only 'cp936'. > > CPython recognises 'mac_roman', 'mac_greek', etc. > IronPython doesn't. > > After a [rare] flash of i

[IronPython] IronPython codec names not compatible with CPython

2006-10-07 Thread John Machin
CPython recognises both 'gbk' and 'cp936' i.e. unicode('some string', 'gbk') does what you'd expect. IronPython 1.0.1 recognises only 'cp936'. CPython recognises 'mac_roman', 'mac_greek', etc. IronPython doesn't. After a [rare] flash of inspiration, I tried 'cp1', 'cp10006', etc and IronPy