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 r.david.murray
Recipients eric.araujo, ezio.melotti, l0nwlf, lemburg, maker, r.david.murray
Date 2011-05-22.18:12:25
SpamBayes Score 1.8938216e-07
Marked as misclassified No
Message-id <1306087946.52.0.618021205144.issue8898@psf.upfronthosting.co.za>
In-reply-to
Content
euc_jp and euc_kr seem to be backward (that is, codecs translates them to the _ version, instead of translating the _ version to the - version).  I worry that there might be other deviations from the standard email names.  I would suggest we pull the list of preferred MIME names from the IANA charset registry and make a test out of them in the email package.  If changing the name returned by codecs is determined to not be acceptable, then those entries will need to remain in the charset module ALIASES table and the codecs-check logic adjusted accordingly.

Unfortunately the IANA registry does not list MIME names for all of the charsets in common use, and the canonical names are not always the ones commonly used in email.  Hopefully the codecs registry is using the most common name for those, and hopefully if there are differences it won't break any user code, since any reasonable email code should be coping with the aliases in any case.

Ezio, if you want to steal this one from me, that's fine by me.
History
Date User Action Args
2011-05-22 18:12:26r.david.murraysetrecipients: + r.david.murray, lemburg, ezio.melotti, eric.araujo, l0nwlf, maker
2011-05-22 18:12:26r.david.murraysetmessageid: <1306087946.52.0.618021205144.issue8898@psf.upfronthosting.co.za>
2011-05-22 18:12:26r.david.murraylinkissue8898 messages
2011-05-22 18:12:25r.david.murraycreate