This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author loewis
Recipients ishimoto, lemburg, loewis, methane, r.david.murray, serhiy.storchaka, t2y, vstinner
Date 2014-12-15.21:48:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1418680109.23.0.696958135422.issue23050@psf.upfronthosting.co.za>
In-reply-to
Content
Another traditional issue with Japanese codecs is that people have different opinions on what the encoding should do. It may be that when we release the codec, somebody comes up and says that the codec is incorrect, and it should do something different for some code points, citing some other applications which he considers right. In particular for the Microsoft ones, people may claim that some version of Windows did things differently.

Now, for this set, the ones that got registered with IANA sound ok (in the sense that it is our bug if they fail to conform to the IANA spec, and IANA's fault if they fail to do what users expect). For the other ones, I wonder whether there is some official source that can be consulted for correctness.

On a different note: why do you claim that the code is written by Perky? (it's not you, is it?)
History
Date User Action Args
2014-12-15 21:48:29loewissetrecipients: + loewis, lemburg, ishimoto, vstinner, r.david.murray, methane, serhiy.storchaka, t2y
2014-12-15 21:48:29loewissetmessageid: <1418680109.23.0.696958135422.issue23050@psf.upfronthosting.co.za>
2014-12-15 21:48:29loewislinkissue23050 messages
2014-12-15 21:48:28loewiscreate