Marc-Andre Lemburg added the comment: On 24.04.2015 10:34, Behdad Esfahbod wrote: > > Thanks Marc-Andre. If the x_ was indeed added for that reason, it's quite a > coincidence, because the MIME name of these encodings also starts with > x-mac-..., so I assumed that's where the x_ comes from.
Oh, I didn't know that :-) Hmm, I can't find the names listed as IANA charset, so the "x-" prefix then probably means non-standard. http://www.iana.org/assignments/character-sets/character-sets.xhtml > The mappings are available at the Unicode website: > http://unicode.org/Public/MAPPINGS/VENDORS/APPLE/JAPANESE.TXT > http://unicode.org/Public/MAPPINGS/VENDORS/APPLE/CHINTRAD.TXT > http://unicode.org/Public/MAPPINGS/VENDORS/APPLE/KOREAN.TXT > http://unicode.org/Public/MAPPINGS/VENDORS/APPLE/CHINSIMP.TXT > > As for actual use, they are part of the OpenType standard. So by user > request, I had to implement them last week in the FontTools Python library. > This is useful for people when dealing with old and legacy fonts, specially > in the process of converting them to Unicode-compatible fonts. This may be an indication that it's better to put those codecs into a PyPI package, rather than Python itself. The above tables are huge (as most Asian codec tables). ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue24041> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
