CVS: tmda/TMDA/pythonlib/email Charset.py,1.8,1.9
"Jason R. Mastaler" <[email protected]>
| Newsgroups | gmane.mail.spam.tmda.cvs |
|---|---|
| Message-ID | <[email protected]> |
Update of /cvsroot/tmda/tmda/TMDA/pythonlib/email
In directory sc8-pr-cvs1:/tmp/cvs-serv5473/TMDA/pythonlib/email
Modified Files:
Charset.py
Log Message:
Deprecate JapaneseCodecs in favour of CJKCodecs.
Literally 90 seconds after I made the last checkin, Tokio Kikuchi
responded to the email-sig list with a thumbs up for replacing
JapaneseCodecs with CJKCodecs. Isn't that always how it works?
If I wouldn't have made the checkin, he wouldn't have responded..
Index: Charset.py
===================================================================
RCS file: /cvsroot/tmda/tmda/TMDA/pythonlib/email/Charset.py,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- Charset.py 26 Nov 2003 00:08:31 -0000 1.8
+++ Charset.py 26 Nov 2003 00:39:50 -0000 1.9
@@ -89,20 +89,14 @@
}
# Map charsets to their Unicode codec strings. Note that Python
-# doesn't come with any Asian codecs by default. Here's where to get
-# them:
-#
-# Chinese/Korean - CJKCodecs (http://cjkpython.i18n.org/)
-# Japanese - JapaneseCodecs (http://www.asahi-net.or.jp/~rd6t-kjym/python)
+# doesn't come with any Asian codecs by default. The CJKCodecs
+# package available at http://cjkpython.i18n.org/ provides a unified
+# unicode codec set for Chinese, Japanese and Korean encodings.
CODEC_MAP = {
- # cjkcodecs isn't ready to replace JapaneseCodecs yet
- #'euc-jp': 'cjkcodecs.euc-jp',
- #'iso-2022-jp': 'cjkcodecs.iso-2022-jp',
- #'shift_jis': 'cjkcodecs.shift_jis',
- 'euc-jp': 'japanese.euc-jp',
- 'iso-2022-jp': 'japanese.iso-2022-jp',
- 'shift_jis': 'japanese.shift_jis',
+ 'euc-jp': 'cjkcodecs.euc-jp',
+ 'iso-2022-jp': 'cjkcodecs.iso-2022-jp',
+ 'shift_jis': 'cjkcodecs.shift_jis',
'euc-kr': 'cjkcodecs.euc-kr',
'ks_c_5601-1987': 'cjkcodecs.cp949',
'iso-2022-kr': 'cjkcodecs.iso-2022-kr',