➜

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 kxroberto
Recipients kxroberto
Date 2011-11-19.11:35:11
SpamBayes Score 0.00075216824
Marked as misclassified No
Message-id <1321702512.61.0.807104309131.issue13432@psf.upfronthosting.co.za>
In-reply-to
Content 
"unicode" seems not to be an official unicode encoding name alias.
Yet it is quite frequent on the web - and obviously means UTF-8. 
(search '"text/html; charset=unicode"' in Google)
Chrome and IE display it as UTF-8.  (Mozilla as ASCII, thus mixed up chars).

Should it be added in to aliases.py ?

--- ./aliases.py
+++ ./aliases.py
@@ -511,6 +511,7 @@
     'utf8'               : 'utf_8',
     'utf8_ucs2'          : 'utf_8',
     'utf8_ucs4'          : 'utf_8',
+    'unicode'            : 'utf_8',
 
     # uu_codec codec
     'uu'                 : 'uu_codec',
History
Date User Action Args
2011-11-19 11:35:12kxrobertosetrecipients: + kxroberto
2011-11-19 11:35:12kxrobertosetmessageid: <1321702512.61.0.807104309131.issue13432@psf.upfronthosting.co.za>
2011-11-19 11:35:12kxrobertolinkissue13432 messages
2011-11-19 11:35:11kxrobertocreate