16947 2012-05-06 18:01:53 +0000 Consider adding U+327E to the Korean index 2015-08-19 10:56:27 +0000 1 1 1 Unclassified WHATWG Encoding unspecified All All RESOLVED WONTFIX P2 normal Unsorted 1 pub-w3 annevk jshin mike sideshowbarker+encodingspec oldest_to_newest 67356 0 pub-w3 2012-05-06 18:01:53 +0000 The current version of the Korean index reflects KS X 1001:1998. Perhaps U+327E (CIRCLED HANGUL IEUNG U), the new Korean postal code symbol added to KS X 1001:2002 (Row 2, Column 72), should be included. 81334 1 annevk 2013-01-14 11:53:44 +0000 Is there any browser that supports this? 81354 2 pub-w3 2013-01-14 20:12:39 +0000 No, not to my knowledge. 81385 3 annevk 2013-01-15 10:18:45 +0000 Then this does not seem worth it. 119704 4 jshin 2015-04-20 21:16:17 +0000 Re-opening: I'm gonna add this to Chrome's copy of ICU. I simply overlooked this. When I worked on Firefox in early 2000, I did add U+327E to Firefox's EUC-KR table. I don't know if it has been dropped since. 119705 5 jshin 2015-04-20 21:27:27 +0000 The EUC-KR position for U+327E is 0xA2 0xE8. index-euc-kr.txt needs one line after 6436 6437 0x327E ㉾ Circled Hangul Ieung U 120072 6 annevk 2015-05-05 14:01:29 +0000 I don't understand why. None of Chrome, Firefox, and Safari support this. 120073 7 1599 annevk 2015-05-05 14:02:04 +0000 Created attachment 1599 testcase 120273 8 jshin 2015-05-12 18:43:22 +0000 Ok. My memory was wrong. I added (or asked to add) two characters added to KS X 1001:1998 (U+327F and one more) to a couple of converters (glibc-iconv and mozilla) in early 2000's [0]. However, I didn't push U+327F (that was added in 2002 to KS X 1001) until 2007. glibc-iconv picked it up and added that to its EUC-KR/ISO-2022-KR/CP949 tables in 2007 [1]. As for Mozilla, I filed a bug ( https://bugzilla.mozilla.org/show_bug.cgi?id=369142 ) around the same time (in 2007) but never fixed it. New Korean fonts do cover it (obviously, the font support is NOT related to this issue, though). Now back to this issue: Practically speaking, it does not matter given that UTF-8 is getting more and more popular. Besides, the number of documents with 0xA2 0xE8 in EUC-KR would be very small, too. So, I don't have a case for this other than my desire to make EUC-KR cover all the characters in the latest KS X 1001 (in 2002). [0] https://bugzilla.mozilla.org/show_bug.cgi?id=134749 : fixed in 2002 [1] https://sourceware.org/bugzilla/show_bug.cgi?id=3954 120275 9 jshin 2015-05-12 19:06:04 +0000 The last paragraph should read: So, I don't have a case for this other than my desire to get U+327E more widely used in Korean documents (in whatever encoding) and make HTML5's EUC-KR cover all the characters in the latest KS X 1001 (in 2002). 122654 10 annevk 2015-08-19 10:56:27 +0000 I think telling folks to use utf-8 is more productive as that also works in older clients. 1599 2015-05-05 14:02:04 +0000 2015-05-05 14:02:04 +0000 testcase euc-kr-circled-hangul-ieung-u.html text/html 87 annevk PG1ldGEgY2hhcnNldD1ldWMta3I+oug8c2NyaXB0PmFsZXJ0KGVuY29kZVVSSShkb2N1bWVudC5i b2R5LmZpcnN0Q2hpbGQuZGF0YSkpPC9zY3JpcHQ+