Rick McGowan wrote: > #12 UTF-16 for Processing > by Markus Scherer
I was a bit surprised to find that Python was listed as using UTF-16 (for the internal representation) with the only reference to it being an unofficial write-up. Markus may not have had a chance to take a look at two references given back in July (on another mailing list). > Python's use of UTF-16(actually UCS-2) for the internal string > represenation appears to be going away. See > http://mail.nl.linux.org/linux-utf8/2003-07/msg00113.html > Even if it's not going away, Python doesn't seem to be > a typical case to take an example of. > See also http://www.egenix.com/files/python/Unicode-EPC2002-Talk.pdf > (page 15 and page 27). Jungshik
