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 ezio.melotti, georg.brandl, kxroberto, loewis, vstinner
Date 2011-11-25.08:22:26
SpamBayes Score 1.5754795e-05
Marked as misclassified No
Message-id <1322209347.38.0.890598120907.issue13432@psf.upfronthosting.co.za>
In-reply-to
Content
I wonder where is the origin, who is the inventor of the frequent charset=unicode? But:


"Sorry, but it's not obviously that Unicode means UTF-8."

When I faced
<meta content="text/html; charset=unicode" http-equiv="Content-Type"/>
the first time on the web, I guessed it is UTF-8 without looking. It even sounds colloquially reasonable ;-)  And its right 99.999% of cases. 
(UTF-16 is less frequent than this non-canonical "unicode")


"Definitely; this will just serve to create more confusion for beginners over what a Unicode string is:
unicodestring.encode('unicode')   <- WTF?"

I guess no python tutorial writer or encoding menu writer poses that example. That string comes in on technical paths:  web, MIME etc.
In the aliases.py there are many other names which are not canonical. frequency > convenience > alias


"Joining the chorus: people who need it in their application will have to add it themselves (monkeypatching the aliases dictionary as appropriate)."

Those people first would need to be aware of the option: Be all-seeing, or all wait for the first bug reports ...  


Reverse question: what would be the minus of having this alias?
History
Date User Action Args
2011-11-25 08:22:27kxrobertosetrecipients: + kxroberto, loewis, georg.brandl, vstinner, ezio.melotti
2011-11-25 08:22:27kxrobertosetmessageid: <1322209347.38.0.890598120907.issue13432@psf.upfronthosting.co.za>
2011-11-25 08:22:26kxrobertolinkissue13432 messages
2011-11-25 08:22:26kxrobertocreate