2009/12/7 John Bond <[email protected]>: > Hi Anthony, > Ok, I'll find myself an SVN client and download the latest. > >> First, I think UTF-8 and UTF-16 are "standard" encodings so they > > They are, and they're available to my frozen app. The problem is that > Windows consoles use different names for them, which Python doesn't > recognise (though really it should). For example, if I want Unicode in my > console, I have to set it to utf-8 (that's the only fully encodable Unicode > encoding that Windows consoles support) which Windows calls "codepage > 65001". I do that with a "chcp 65001" command. When I run Python it gets the > current console codepage from Windows ("cp65001") and doesn't recognise the > name unless I've edited aliases.py to tell it that "cp65001" = "utf-8". > It's strange that Python doesn't come with knowledge of the name of the only > proper Unicode console encoding in Windows, but that's the way it is!
I suppose it's because they are not defined by IANA: http://www.iana.org/assignments/character-sets The aliases.py file says: The following aliases dictionary contains mappings of all IANA character set names for which the Python core library provides codecs. In addition to these, a few Python specific codec aliases have also been added. (IANA, of course, being the Internet Assigned Numbers Authority.) -- Michael Wood <[email protected]> ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ cx-freeze-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cx-freeze-users
