(Ah, the joy of trying to get those RTL languages into the Summary line...) ICANN has approved four new TLDs, which are IDNs. We should find out what "shape" they intend to use for their registrations, and add the appropriate entries to the PSL. They have already contacted us for IDN TLD whitelist inclusion, so we have people we can ask. Gerv
"Thanks for your clarification ... For our new IDN label we will start with option1 (Flat) but might enable 3rd levels in the future (we have reserved some names for that purpose). So the list should have the following entries: // xn--mgberp4a5d4ar : http://www.nic.net.sa/ السعودية BTW for .sa we are going to open 2LD registration at the end of this year. Here are the updated entries for .sa ccTLD: // sa : http://www.nic.net.sa/ sa com.sa net.sa org.sa gov.sa med.sa pub.sa edu.sa sch.sa So is there anything else I should do? With best regards, Raed I. Al-Fayez"
Actually, there's a whole load of these in the pipeline: http://www.icann.org/en/topics/idn/fast-track/string-evaluation-completion-en.htm Gerv
Dear Gervase, After consulting our management we don't think we will use 3LD in the new IDN ccTLD for Saudi Arabia. So there are no need to add the reserved name to the list. With best regards, Raed I. Al-Fayez
(In reply to comment #4) > This is bug 563309, bug 564213, bug 564214 and bug 564240. No, these bugs are for adding IDN-capable TLD's to the network.IDN.whitelist configuration in about:config. This bug is about the Public Suffix list, used for defining second-level TLD's, as seen in <http://publicsuffix.org/>
pkasting: as you know, because the default rule applies, just adding these new TLDs to the PSL makes no functional difference. But we should probably do it anyway, as "placeholders". Does that make sense to you? Gerv
Actually, in Chrome this makes a great difference, because without this, people who type in these new addresses won't navigate by default. So I'd like to see this ASAP. I should have written a patch myself, I've just been busy with other stuff :/
Created attachment 447346 [details] [diff] [review] patch v1 Here's my attempt at a patch. This adds the four IDNs, alphabetized by their punycode representation. It also adds the "sa" entry for upcoming registration of 2LDs. The reference links on these are not very great because most of the registrars don't have a ton of documentation on these TLDs.
Comment on attachment 447346 [details] [diff] [review] patch v1 r=gerv. Are you going to do a different part for the 10 or so others referenced in that ICANN document? Gerv
(In reply to comment #9) > Are you going to do a different part for the 10 or so others referenced > in that ICANN document? Are those already approved and ready to go in the wild? I figured we should add things once they were actually OKed or started working, I'm not sure what the status of everything in that document is.
ICANN has approved them; I very much doubt their sponsors would give up now. And I don't see any harm in adding them. Let's do that in a different bug. I'll check this one in soon. Gerv
Comment on attachment 447346 [details] [diff] [review] patch v1 Approved for 22.214.171.124 and 126.96.36.199, a=dveditz for release-drivers
Can someone land on branch for me?
(In reply to comment #14) > Can someone land on branch for me? Sure. In the future, just add the "checkin-needed" keyword.
OK. I normally use that to get things landed on trunk, I wasn't sure if I added it to a Status:Fixed bug if someone would go and land things on branches for me :)