[issue7856] cannot decode from or encode to big5 \xf9\xd8

STINNER Victor added the comment: > It looks like the F9D6–F9FE characters all come from the Big5-ETen extension One option would be to add a new big5eten encoding to Python. Someone has to implement the code. -- ___ Python tracker

[issue7856] cannot decode from or encode to big5 \xf9\xd8

Max Bolingbroke added the comment: As of Python 3.7.9 this also affects \xf9\xd6 which should be \u7881 in Unicode. This character is the second character of 宏碁 which is the name of the Taiwanese electronics manufacturer Acer. You can work around the issue using big5hkscs just like with the o

[issue7856] cannot decode from or encode to big5 \xf9\xd8

Martin v. Löwis added the comment: Inndy, you might also be talking about big5-2003, from http://www.csie.ntu.edu.tw/~r92030/project/big5/ Python currently does not support big5-2003, but a contribution of such an encoding would surely be welcome. -- _

[issue7856] cannot decode from or encode to big5 \xf9\xd8

Martin v. Löwis added the comment: I'm still looking for an official source of that. >>> u"\u88cf".encode("big5hkscs") '\xf9\xd8' works fine (and always has been working fine), and the character clearly is in big5hkscs. According to http://en.wikipedia.org/wiki/Big5 F9D8 is "Reserved for us

[issue7856] cannot decode from or encode to big5 \xf9\xd8

Inndy added the comment: I'm Taiwanese, F9D8 in big5 should be mapped to E8A38F in UTF-8. -- nosy: +Inndy ___ Python tracker ___ ___ Py

[issue7856] cannot decode from or encode to big5 \xf9\xd8

Changes by Antoine Pitrou : -- nosy: +haypo versions: +Python 2.7, Python 3.2, Python 3.3 -Python 2.6 ___ Python tracker ___ ___ Python

[issue7856] cannot decode from or encode to big5 \xf9\xd8

Changes by Kang-Hao (Kenny) Lu : -- nosy: +kennyluck ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue7856] cannot decode from or encode to big5 \xf9\xd8

Roumen Petrov added the comment: > That iconv supports it is not convincing, ... GNU libc is not convincing . What you talking about ? -- nosy: +rpetrov ___ Python tracker ___ _

[issue7856] cannot decode from or encode to big5 \xf9\xd8

Martin v. Löwis added the comment: perky, what do you think? -- assignee: -> hyeshik.chang nosy: +hyeshik.chang ___ Python tracker ___ __

[issue7856] cannot decode from or encode to big5 \xf9\xd8

Xuefer x added the comment: sure after enlighten by your url which is OBSOLETE see: http://www.unicode.org/Public/MAPPINGS/EASTASIA/ReadMe.txt i found http://unicode.org/charts/unihan.html then http://www.unicode.org/Public/UNIDATA/ then http://www.unicode.org/Public/UNIDATA/Unihan.zip in side t

[issue7856] cannot decode from or encode to big5 \xf9\xd8

Martin v. Löwis added the comment: In particular, the Unicode consortium mapping table, now at http://www.unicode.org/Public/MAPPINGS/OBSOLETE/EASTASIA/OTHER/BIG5.TXT doesn't map f9d8 to anything; the current version of that table (in unihan.zip) has these mappings for U+88CF: U+88CF kCCCII

[issue7856] cannot decode from or encode to big5 \xf9\xd8

Martin v. Löwis added the comment: That iconv supports it is not convincing, IMO. Do you have other sources (like tables in the web somewhere) that support your request? -- nosy: +loewis ___ Python tracker ___

[issue7856] cannot decode from or encode to big5 \xf9\xd8

New submission from Xuefer x : using iconv: $ printf "\xf9\xd8" | iconv -f big5 -t utf-8 | xxd 000: e8a3 8f ... $ printf "\xe8\xa3\x8f" | iconv -f utf-8 -t big5 | xxd 000: f9d8 .. using python >>> print "\xf9\xd8".decod