Issue 1409538: email.Charset.py CODEC_MAP no longer requires 'japanese' (original) (raw)

Created on 2006-01-19 00:35 by tkikuchi, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (4)
msg27316 - (view)	Author: Tokio Kikuchi (tkikuchi)	Date: 2006-01-19 00:35
The commonly used JapaneseCodecs no longer requires 'japanese' prefix in codec specification. On the other hand if a user install CJKCodecs instead of JapaneseCodecs, 'japanese' prefix cause error. This was already fixed in email-3.0 (Python 2.4) but should be fixed in email-2.5.x if we want to support mailman-2.2 for Python 2.3. It looks like 'korean' can also be stripped. See attached patch.
msg27317 - (view)	Author: Tokio Kikuchi (tkikuchi)	Date: 2006-02-08 00:06
Logged In: YES user_id=67709 Looks like we should retain CODEC_MAP in order to properly encode Japanese text into iso-2022-jp (canonical japanese message charset). We need lines like this: CODEC_MAP = { 'euc-jp': 'euc-jp', 'iso-2022-jp': 'iso-2022-jp', ... 'us-ascii': None }
msg27318 - (view)	Author: Barry A. Warsaw (barry) *	Date: 2006-02-08 03:07
Logged In: YES user_id=12800 The attached patch addresses the issue both in this issue and in 1409544. It's a bit more extensive because it tries to figure out whether the Japanese and Korean codecs are available under their Python 2.4 names or under their old names. I've run this test under all Pythons from 2.1 to 2.5, albeit without the third party codecs under anything before 2.4.
msg27319 - (view)	Author: Barry A. Warsaw (barry) *	Date: 2006-02-08 13:35
Logged In: YES user_id=12800 r42270 for email 2.5/Python 2.3. I will forward port to Python 2.4 and 2.5 (email 3.0) as appropriate.