First Non-Latin TLDs Go Online Today
eldavojohn writes "ICANN today switched on the country code top level domains for Egypt, Saudi Arabia, and the United Arab Emirates, which are the first non-Latin TLDs available and are also fully readable right to left. Slashdot does not support them but you can find the TLDs in the BBC article. ICANN said it had 21 more requests for TLDs in 11 different languages. A quick note — if you do not have the language packs installed, you may experience unpredictable browser behavior in the URL bar. Right now countries like China and Thailand have implemented workarounds to achieve the same effect."
It is now possible to get a domain that cannot be slashdotted!
Well, hooray for a more fragmented Internet. While every keyboard can type A-Za-z, that's not true of Chinese or Arabic, so sites using those TLDs will be effectively off-limits to those that aren't "native". Sure, the sites can also register an ordinary domain name, but then why not just use that domain name to begin with?
they didn't break backwards compatability,
here's the brilliant standard http://en.wikipedia.org/wiki/Punycode
it's just awesome.
Ridiculous tribalism, that's all it is. Fragmentation of the Internet to appease some regressive, regional e-peenery is the stupidest idea to date. I speak 8 languages and love some, like Russian immensely, but the internet is a nation with its own language, and that language is Standard English. I call shenanigans on anything else being shoehorned into its basic infrastructure!
"Remember when I said I would never lie? Well, that was the first time."
Yeah, like www.bankofamerica.com.secure.cn
I have a better one: www.bankofamerica.com.secure.ru.
It has an algorithm that predicts what expenses you will have in the near future and withdraws your money and puts it in a safe account that's unknown to you so that you don't spend it. They did that to me - took all my money out - and then all I have to do is send them an email and they'll pay my bills - all for a $19.95 monthly service fee on my CC. I can't loose!
This is my first month on this program, so I'll let you guys know how it works.
RIP America
July 4, 1776 - September 11, 2001
The ICANN blog has a working link.
Here you go: http://xn--4gbrim.xn----rmckbbajlc6dj7bxne2c.xn--wgbh1c/ar/default.aspx
Learning HOW to think is more important than learning WHAT to think.
Guess what -- this will all get blocked. More fragmentation = less free internet. Here comes Sharia law that says all internet usage must be in Farsi, and all websites with latin endings will be blocked. Weak.
For the inhabitants of Mönsterås, Sweden.
The town name means 'patterned ridge', but to date they've have had to put up with the domain "Monsteras" - which means "monster-carcass".
(å, ä, ö/ø in the Scandinavian languages are considered to be their own unique characters, not accented 'a's and 'o's.)
currently people are not getting on the internet because its all in english: it serves as a barrier and they see no reason to even try
but when the internet supports their native language, they get on the internet, get a taste of it, like it, want to use more it, and inevitably this drives them to the english web, since there's more of whatever they're looking for over there
in other words, the long term effect of supporting other languages on the web is paradoxically further and faster consolidation to english
intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
Except there *IS* an escape sequence. And the actual representation is in standard latin alphabets.
The reason is that browsers can detect the escape sequence and interpret the rest of the URL as a unicode string.
The escape is "xn--" - domains using it have xn--domain, TLDs as xn--TLD. Use both and they both have to be escaped - xn--blah.xn--blahtld.
The trick for the Rest of Us is to be able to set that as "off" by default to keep these xn-- sequences from looking like normal latin characters. The good news is the encoding is such that Paypal and the like don't get rendered as xn--paypal.com and such, but xn--junk_that_renders_as_paypal.com.
Internationalized domain names have been around a few years. This is just an internationalized TLD using the same DNS-friendly encoding scheme.
I got a better one. www.bankofamerica.com. See, I used Unicode character 212e instead of the e. Looks the same to most people, and would probably fool quite a bit of people. I wonder how they hope to stop situations like this. (I actaully used an e, because slashdot wouldn't let me put in the HTML entity, but this is good enough to demonstrate the problem)
Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
So, if you only could have done it, you might have done it.
Now I'm really scared.
You are welcome on my lawn.
SPQR://
I am TheRaven on Soylent News
I have an even better one: www.bankofamerica.com
It has an algorithm that increases my taxes and deposits the money into their executive bonus pool.
As I maintain my own DNS servers and such, I was curious how this worked. Here's what I learned with 15 minutes of research:
My first stop was to see the root.zone and I looked for these new TLDs, curious to see how they would show up in a Latin-based zone file. Ah, I spotted these odd XN-- zones and then knew what to dig into more.
Take for instance (I pasted a Unicode domain, but Slashcode won't show it) which is handled by ns[1-3].dotmasr.eg.:
$ dig ns (Unicode domain)
; > DiG 9.6.2-P1-RedHat-9.6.2-3.P1.fc12 > ns (Unicode domain) ;; QUESTION SECTION: ;.(Unicode domain) IN NS ;; ANSWER SECTION:
. 3600(Unicode domain) IN NS ns1.dotmasr.eg.
. 3600 (Unicode domain)IN NS ns2.dotmasr.eg.
. 3600(Unicode domain) IN NS ns3.dotmasr.eg.
If you look in the root.zone file, you will see that the ASCII/Latin version of this zone is really XN--WGBH1C.:
XN--WGBH1C. NS NS1.DOTMASR.EG.
XN--WGBH1C. NS NS2.DOTMASR.EG.
XN--WGBH1C. NS NS3.DOTMASR.EG.
TLD Reserved Domains has a list of the current mappings. ToASCII and ToUnicode are the methods to convert back and forth which links to RFC 3490 which has the nitty gritty details.
(meh, Slashcode doesn't support Unicode encoding, but I can see the Unicode domain name I am pasting in before I hit Preview in Firefox)
Also, the whole switching from right to left in Latin characters to left to right in some Unicode is odd when trying to edit!
Phishing aside I would say the biggest concern here is the fact we are effectively walling off parts of the internet for respective regions.
On the Oregon Cost born and raised, On the beach is where I spent most of my days
Wouldn't the Latin URL start off with "HTTPUS" for the URLUS?
Only works if your DNS server is properly configured to return the proper IP addressus
CCXVI.XXXIV.CLXXXI.XLV
Every mans' island needs an ocean; choose your ocean carefully.