This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 16947 - Consider adding U+327E to the Korean index
Summary: Consider adding U+327E to the Korean index
Status: RESOLVED WONTFIX
Alias: None
Product: WHATWG
Classification: Unclassified
Component: Encoding (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: Unsorted
Assignee: Anne
QA Contact: sideshowbarker+encodingspec
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-06 18:01 UTC by pub-w3
Modified: 2015-08-19 10:56 UTC (History)
2 users (show)

See Also:

Attachments
testcase (87 bytes, text/html)
2015-05-05 14:02 UTC, Anne 		Details

Description pub-w3 2012-05-06 18:01:53 UTC 
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.
Comment 1 Anne 2013-01-14 11:53:44 UTC 
Is there any browser that supports this?
Comment 2 pub-w3 2013-01-14 20:12:39 UTC 
No, not to my knowledge.
Comment 3 Anne 2013-01-15 10:18:45 UTC 
Then this does not seem worth it.
Comment 4 Jungshik Shin 2015-04-20 21:16:17 UTC 
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.
Comment 5 Jungshik Shin 2015-04-20 21:27:27 UTC 
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
Comment 6 Anne 2015-05-05 14:01:29 UTC 
I don't understand why. None of Chrome, Firefox, and Safari support this.
Comment 7 Anne 2015-05-05 14:02:04 UTC 
Created attachment 1599 [details]
testcase
Comment 8 Jungshik Shin 2015-05-12 18:43:22 UTC 
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
Comment 9 Jungshik Shin 2015-05-12 19:06:04 UTC 
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).
Comment 10 Anne 2015-08-19 10:56:27 UTC 
I think telling folks to use utf-8 is more productive as that also works in older clients.