Closed
Bug 863171
Opened 12 years ago
Closed 12 years ago
Korean IDN Country Code (.한국) does NOT exists.
Categories
(Core Graveyard :: Networking: Domain Lists, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: bluekyu.dev, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.12) Gecko/20100101 Firefox/10.0.12 Iceweasel/10.0.12
Build ID: 20130119084230
Steps to reproduce:
I entered web address with Korean IDN Country Code (.한국).
Actual results:
Korean IDN Coutnry Code (한국 ("Hanguk"), encoded as "xn--3e0b707e" ) converted to a punycode.
Expected results:
In a list of top-level domains (TLDs), Korean ASCII Country Code (.kr) already exists.
However, Korean IDN Country Code (.한국) does NOT exists, so the address with '.한국' converts to a punycode.
The Korean IDN Country Code (.한국) approved at 2011-01-25.
(https://community.icann.org/pages/viewpage.action?pageId=31173165)
Another browsers already support that, but firefox does not support it yet.
Comment 1•12 years ago
|
||
.한국 does exists, it's even mentioned in the Public Suffix List. But it's not mentioned in the IDN whitelist (even though .kr is). At this moment, Mozilla requires that each TLD is approved separately because not every TLD is safe to use. For example, .com got recently approved but that decision is reversed again in bug 843739, exactly because some unsafe domain-names have been discovered.
I could not find any good indicator of what characters are allowed in .한국 . http://www.nic.or.kr/jsp/english/domain/faq.jsp#faq07 mentions the Hanguel characterset, but it has 11,172 characters, while .kr only has 2,350 syllables.
Note that any change should be requested by someone from KRNIC.
Comment 2•12 years ago
|
||
We now have an algorithmic method of determining IDN suitability, and so we are no longer accepting additions to the whitelist. See https://wiki.mozilla.org/IDN_Display_Algorithm for more details.
Gerv
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
| Reporter | ||
Comment 3•12 years ago
|
||
Thank you, Markham.
I confirmed that this bug has been resolved since Firefox 22.
Updated•1 year ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•