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 Artoria2e5
Recipients Artoria2e5, ezio.melotti, vstinner
Date 2016-11-16.05:40:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1479274828.26.0.726447169651.issue28712@psf.upfronthosting.co.za>
In-reply-to
Content
Mappings for 0x81 and 0x8D in multiple Windows code pages diverge from what Windows does. Attached is a script that tests for this behavior. (These two bytes are not necessary the only problems, but for sure they are the most widespread and famous ones. Again, refer to Unicode best fit for something that works.)

This problem is seen in Python 2.7.10 on Windows 10b14959, but apparently it is known since long ago[1]. Python 3.4.3 on Cygwin also fails ``b'\x81\x8d'.encode('cp1252')``.
  [1]: https://ftfy.readthedocs.io/en/latest/#module-ftfy.bad_codecs.sloppy
History
Date User Action Args
2016-11-16 05:40:28Artoria2e5setrecipients: + Artoria2e5, vstinner, ezio.melotti
2016-11-16 05:40:28Artoria2e5setmessageid: <1479274828.26.0.726447169651.issue28712@psf.upfronthosting.co.za>
2016-11-16 05:40:28Artoria2e5linkissue28712 messages
2016-11-16 05:40:27Artoria2e5create