[issue29456] bug in unicodedata.normalize: u1176, u11a7 and u11c3

Wonsup Yoon added the comment: Ok, I'll do it. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue29456] bug in unicodedata.normalize: u1176, u11a7 and u11c3

Xiang Zhang added the comment: We have moved our code hosting to GitHub, would you mind turn your patch into a GitHub PR first Wonsup? -- ___ Python tracker ___

[issue29456] bug in unicodedata.normalize: u1176, u11a7 and u11c3

Wonsup Yoon added the comment: Is there anything need more? -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue29456] bug in unicodedata.normalize: u1176, u11a7 and u11c3

Changes by Serhiy Storchaka : -- nosy: +lemburg, loewis stage: -> patch review type: -> behavior versions: +Python 3.5, Python 3.7 ___ Python tracker ___ __

[issue29456] bug in unicodedata.normalize: u1176, u11a7 and u11c3

Changes by Wonsup Yoon : -- title: bug in unicodedata.normalize: u1176 -> bug in unicodedata.normalize: u1176, u11a7 and u11c3 ___ Python tracker ___ ___

[issue29456] bug in unicodedata.normalize: u1176

Wonsup Yoon added the comment: I think you are right. The modern final consonants is [11a8..11c2]. I attached another patch for this issue. -- Added file: http://bugs.python.org/file46536/u11a7u11c3.patch ___ Python tracker

[issue29456] bug in unicodedata.normalize: u1176

Xiang Zhang added the comment: How about the third character's range? The code seems assuming it's [11a7..11c3] while the spec is [11a8..11c2]? >>> unicodedata.normalize("NFC", "\u1100\u1175\u11a7") '기' while it should be '기ᆧ'? -- nosy: +xiang.zhang __

[issue29456] bug in unicodedata.normalize: u1176

New submission from Wonsup Yoon: unicodedata can't normalize(NFC) hangul strings which contain \u1176(HANGUL JUNGSEONG A-O). >>> from unicodedata import normalize >>> normalize("NFC", "\u1100\u1176\u11a8") '깍' => should be "\u1100\u1176\u11a8" not '깍' (\uae4d) I attached a patch for this issu