➜

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 t2y
Recipients ishimoto, methane, r.david.murray, t2y
Date 2014-12-14.16:28:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAGBzy2p7MUHGc6zcqK0Up5TAsJOd2BEj0v2ZY8ALpOKZDoZarQ@mail.gmail.com>
In-reply-to <1418573079.05.0.448418438534.issue23050@psf.upfronthosting.co.za>
Content 
On Mon, Dec 15, 2014 at 1:04 AM, R. David Murray <report@bugs.python.org> wrote:
> In emails these are labeled as, say, iso-2022-jp-ms?

No. These are labeled just 'iso-2022-jp' and we (japanese) choose
proper charset encoding to decode the encoded text. You can see
several variants of iso-2022-jp. Yes, that's a very strange, but it's
a historical reason.

http://en.wikipedia.org/wiki/ISO/IEC_2022#ISO.2FIEC_2022_character_sets

> See also issue 8898 with regards to email encodings.

Therefore, this is different issue.
History
Date User Action Args
2014-12-14 16:28:43t2ysetrecipients: + t2y, ishimoto, r.david.murray, methane
2014-12-14 16:28:43t2ylinkissue23050 messages
2014-12-14 16:28:42t2ycreate