Message 332285 - Python tracker

➜

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	blkserene
Recipients	blkserene, ezio.melotti, vstinner
Date	2018-12-21.10:08:12
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1545386892.27.0.788709270274.issue35551@psf.upfronthosting.co.za>
In-reply-to

Content
There're some minor issues about encodings supported by Python. 1. "tis260" is the alias for "tactis", where "tis260" might be a typo, which should be tis620. And "tactis" is not a supported encoding by Python (and I can't find any information about this encoding on Google). 2. "mac_latin2" and "mac_centeuro" refer to the same encoding (the decoding tables are identical), but they are provided as two encodings in different names ("maccentraleurope" is an alias for "mac_latin2", but "mac_centeuro" isn't). 3. The same problem for "latin_1" and "iso8859_1" ("iso_8859_1" is an alias for "latin_1", but "iso8859_1" isn't).

There're some minor issues about encodings supported by Python.
1. "tis260" is the alias for "tactis", where "tis260" might be a typo, which should be tis620. And "tactis" is not a supported encoding by Python (and I can't find any information about this encoding on Google).
2. "mac_latin2" and "mac_centeuro" refer to the same encoding (the decoding tables are identical), but they are provided as two encodings in different names ("maccentraleurope" is an alias for "mac_latin2", but "mac_centeuro" isn't).
3. The same problem for "latin_1" and "iso8859_1" ("iso_8859_1" is an alias for "latin_1", but "iso8859_1" isn't).

History
Date	User	Action	Args
2018-12-21 10:08:12	blkserene	set	recipients: + blkserene, vstinner, ezio.melotti
2018-12-21 10:08:12	blkserene	set	messageid: <1545386892.27.0.788709270274.issue35551@psf.upfronthosting.co.za>
2018-12-21 10:08:12	blkserene	link	issue35551 messages
2018-12-21 10:08:12	blkserene	create