Several readers including alphadogg tipped the news that ICANN has approved non-Latin ccTLDs at its meeting in Seoul. "Starting in mid-November, countries and territories will be able to apply to show domain names in their native language, a major technical tweak to the Internet designed to increase language accessibility. On Friday, the Internet's addressing authority approved a Fast-Track Process for applying for an IDN (Internationalized Domain Name) and will begin accepting applications on Nov. 16. The move comes after years of technical testing and policy development... Currently, domain names can only be displayed using the Latin alphabet letters A-Z, the digits 0-9 and the hyphen, but in future countries will be able to display country-code Top Level Domains (cc TLDs) in their native language. ... 'The usability of IDNs may be limited, as not all application software is capable of working with IDNs,' ICANN said in a 59-page proposal (PDF) dated Sept. 30 that describes the [application] process." Reader dhermann adds, "Great, now even less chance I can identify NSFW links before they are blocked by my work's big brother app and my boss is notified... again."
Slashdot's web interface is quite embarrassing in this respect. Having a non-Unicode-capable page in 2009 is like having one that is optimized for Netscape 0.9, no matter what amount of JavaScript and Web 2.0 bling they put in there.
If international URLs will finally force Slashdot to implement a triviality such as string parsing, so much the better.
Far too much software makes the assumption that TLDs only contain [a-z0-9-], so if you want to go changing that there needs to be a damn good reason, there is not. There are ~1369 2 letter TLDS to be shared between ~200 soverin states and 49284 3 letter generic ones to be split between uses (.xxx.nws.org.edu, etc), there doesn't seam to be any good reason to expand that and make lots of software more complex.
You don't understand. Punycode is how second-level domains are already implemented, even on top of relatively old browsers. This is an extension of Punycode to be usable in the TLD as well.
In other words, your current version of Firefox will be able to visit pages in IDN TLDs when they're implemented, and so if someone does create a.örg TLD today, you can go to www.anysite.örg to your heart's content already.
Note that this doesn't mean you can go to www.anysite.örg in NCSA Mosaic or anything, because these old browsers were around when Punycode wasn't even a standard. You can go to www.anysite.xn--rg-eka and NCSA Mosaic will recognise that, though. The seamless IDN TLD usage is just going to be present in the more modern browsers. I expect that Opera 8+, IE 6+, Firefox 2+ and recent Safari/Konqueror/Epiphany are going to be able to visit www.anysite.örg and 'hide' the xn--etc- access details from you, the user.
If everyone in the world liked those latin characters, then sure. But maybe someone else in the world prefers yahoo.(nihon*)? Wanted to write it in kanji but/. doesn't seem to take unicode.
Domain names have been muddy for quite some time. Think of all the non commercial dot coms. Or government sites on anything other than their.gov or their country code. del. del.icio.us? They've been mostly ignored. People get.com to look professional,.net at random (though it is supposed to be for ISPs), and.org if you want to stand for some ideal.
Though TBH I'm not certain WHY we need TLDs anyways. It isn't like there is some commercial slashdot.com it just redirects. I imagine that any big name will
Yeah right. Because everybody in the whole world only uses ASCII right?
Sorry for sounding flippant, but such US-myopia is far to prevalent for my liking.... Come on guys: Wake up and smell the coffee! There is more to the world than the US! There is no reason to make most of South East Asia and China 2nd-rate citizens on the internet.
I agree that there is a lot of software that needs changing as a result though. But that just means more work, right? You could probably sell this as an anti-recession measure
You know, except for ease of use for those who don't use Latin characters in their daily lives. But who cares about them? They should just go back to their own country and create their own internet.
if you want to go changing that there needs to be a damn good reason
I don't have any first-hand experience, but according to the BBC story when one enters a native-script domain name into one's browser, the domain name is entered normally (for the locale) and then to enter, e.g., ".in", one needs to press a key combination to shift the keyboard into latin-mode, then, enter the two letters, then shift the keyboard back into native mode.
It's a usability problem. I sure would be annoyed if.com had to be rend
In reality, the new domain names will be stored in the DNS as sequences of letters and numbers beginning xn-- in order to maintain compatibility with the existing infrastructure. The characters following the xn-- will be used to encode a sequence of Unicode characters representing the country name.
Any DNS gurus care to explain why they wouldn't simply use UTF8?
To avoid breaking all the DNS-related code out there that assumes (ie correctly, based on the current spec) only alphanumerics and '-' in each component.
If you wish to rewrite every single bit of DNS-dependent code, in every laptop, server, embedded network device, etc, etc,... well assume that it can't be done, and with this mechanism it doesn't need to be. Though I bet a few bits of code will barf at the '--' anyhow...
Backwards compatibility with existing systems that don't support UTF-8 but still need to make DNS queries. Ranges from basic tools like dig, to un-updated browsers, to embedded devices like routers.
Are there any public DNS servers that support this to see what happens with my existing software??
Since software makes the assumption that TLDs only contain [a-z0-9-] [slashdot.org], UTF-8 can't be used in the DNS. Internationalised domain names, even before these new ccTLDs, used that xn-- system, called Punycode [wikipedia.org]. For instance, the site tinyarro.ws, which provides short URLs via a Unicode domain name, already used.ws for that purpose. It turns into xn--hgi.ws when the DNS request is issued.
ccTLDs using Punycode is just an extension of that mechanism for second-level domains.
Actually, UTF-8 can and is being used in DNS - as long as you stick to basic Latin characters, that is. Also it is Unicode - as I posted earlier, Unicode is a blanket for UTF-8, UTF-16 and UTF-32 which makes it ambiguous.
UTF-8 bits 0-7 is ASCII as long as bit 8 isn't set, so to fully support it you'd need to still exclude bits below 7 that are not valid html characters and include support for multiple bytes and bit 8. The reason existing DNS servers won't work with it is because bit 8 indicates multibyte
The goal is to encode international characters as the characters currently accepted by the standard (a-z, 0-9, etc.) UTF does not do this. Also, the number of characters you can have in a domain name is limited to 26 (and it is the encoded length that counts), so the coding has to be efficient. This is precisely what Punycode [wikipedia.org] is designed to do. Software can recognize an encoded name by the fact that it begins with the special sequence of letters "xn--"
This will only make phishing attacks easier unless there are SERIOUS checks on domain name registrations.
There are letters in the Cyrillic alphabet that have different character codes than their look-alike letters in the Latin alphabet. I'm sure there are other collisions as well. I'm sure they accounted for this in the proposal, but the problem always lies in the implementation.
From a security standpoint, this is a VERY bad idea without proper regulation of domain name registrations, and so far it has been demonstrated that we cannot manage them properly even with only the Latin alphabet.
From a cultural and usability standpoint, this is a good thing. It will be easier for someone whose native language uses a non-Latin alphabet to recognize the supposed purpose of a web site by its domain name if some of those domain names can be in their native language. A hypothetical native Tamil speaker who speaks no English will be able to recognize the purpose of a site with an appropriate domain name in Tamil, for example
There are letters in the Cyrillic alphabet that have different character codes than their look-alike letters in the Latin alphabet. I'm sure there are other collisions as well. I'm sure they accounted for this in the proposal, but the problem always lies in the implementation
This is a decision made by ICANN. We've known for some time that they will willingly approve really tremendously bad ideas, if enough money is presented to them. They recently moved on a motion to start selling gTLDs, after all.
From a security standpoint, this is a VERY bad idea without proper regulation of domain name registrations, and so far it has been demonstrated that we cannot manage them properly even with only the Latin alphabet
Security is not of any concern for ICANN. Never has been, never will be. As long as they keep making money they're happy; security, spam, phishing, etc, be damned.
I think the limitation that nationalized character sets will be restricted to the country TLDs where that language is native is a good first step. Additionally, I believe you're not allowed to use the latin alternative form characters from unicode (like 0xFF20-0xFF5F).
If you're really paranoid, you could just be extra suspicious of domains that end in two letters (and yes, I am including.us), particularly when the 2nd level name is something you recognize, like paypal, ebay, etc. If you're in China, there may indeed be a legitimate paypal.cn, but I suspect it would set off my spidey sense to see a URL like that show up in my e-mail.
If you're really paranoid, you could just be extra suspicious of domains that end in two letters (and yes, I am including.us), particularly when the 2nd level name is something you recognize, like paypal, ebay, etc. If you're in China, there may indeed be a legitimate paypal.cn, but I suspect it would set off my spidey sense to see a URL like that show up in my e-mail.
That won't work. There really are a lot of big companies that have country-specific sites that use the two-letter global domains. For example, if you're after books in German then you might be very interested in visiting amazon.de, which is totally legit.
Yeah, but if you know that you want that, then you'll be expecting it. We're talking about being on the lookout for 2 letter TLDs in places you don't expect them.
This risk can be greatly reduced if they limit domain names to only one alphabet, i.e. Russian domain with Cyrillic ccTLD should have only Cyrillic letters in it.
In many of these countries, they often have two domain names for a website: one that is easy to remember by foreigners, one that is easy to remember by locals (i.e. cyrillic name transliterated to Latin alphabet). The transliterated domain name is usually horrible, sounds weird, and often people transliterate stuff in different ways, so it's often not easy to remember anyway.
You do know that this is for the TLD part of the URL only. The first part of a domain can already be written in non latin scripts, Korean for example but the TLD must but Latin, this decision just enables the.com.kr to be turned into Hangul.
If ICANN did not standardise this then nations will just implement their own systems which will be different and incompatible with each other, much like China and Thailand have already done.
" Within those parts, an octet may be represented by the chararacter which has that octet as its code within the US-ASCII [20] coded character set. In addition, octets may be encoded by a character triplet consisting of the character "%" followed by the two hexadecimal digits (from "0123456789ABCDEF") which forming the hexadecimal value of the octet. (The characters "abcdef" may also be used in hexadecimal encod
Now those countries, organizations and businesses that wish to become inaccessible to most of the world (except the native speakers of their own language) can finally do so as easily as possible. Create their own little Internet reservations and stay there:)
As long as my software (such as Firefox) obligingly converts these IDN urls into the dash-hex notation making them obviously unreadable, I am ok with that.
Disclaimer: I am a native of non-English speaking country. I am sure a few of my countrymen will use this feature based on misplaced patriotism. I am also sure that vast majority will ignore it just like they ignore potential to use non-latin domain names that exists right now.
A lot of the debate here seems to be about English-speaking countries vs. the rest of the world, but English isn't the only language that uses the Latin. Also, the unavailability of non-Latin scripts hasn't hampered the flourishing of home-grown websites in India and China named in their many local languages - what makes the ICANN think this is even necessary?
How exactly do you think you'll be able to type in a URL in mandarin or russian on west european keyboard?
You enable Chinese keyboard layout (dunno what's it called), and type it. The letters printed on the keys of your keyboard aren't some sort of magic that lets your computer input languages written in them, you know.
I don't have any keyboards with Russian characters on them, but I happily type in Russian regardless (in fact, I only first realized that I do actually truly touch type when I first ran into this problem, which turned out to not be a problem in the end).
I'm happy you'll do this. I won't, and the majority of the internet users won't either. It'll just further separate nations, because I won't go through the hassle of typing in a foreign character domain name - it'll just a site I won't visit.
Presumably, if a site is designed to be visited by someone who only understands English, it will use an English TLD. If it uses TLD with national characters, then most likely the content is in the language other than English as well, and you'd need to have means to input that language to fully interact with the site anyway.
"the majority of the internet users won't either."
Sorry, but that sounds like typical American ethnocentricity. The MAJORITY of internet users actually are people who don't natively speak English. Chinese speakers, Russian speakers, European people, many of whom use cyrilic alphabets, Arabs, South Americans, Indians, and others that I'm surely missing.
How can you possibly speak for "the majority of internet users", when people who speak English as their native language constitute a pretty small percentage
First of all any domain name is going to have to be encoded as a stream of bytes somehow because far too much stuff is already implemented to handle the string that way. As others pointed out punycode is used.
Second, UTF-8 is smaller than UTF-16 for all languages, even Chinese. This is because all the ASCII 0x00-0x7F characters are smaller, and therefore the encoding will be smaller if there are more of these than there Unicode 0x800-0xFFFF characters. This seems incorrect for Chinese
I don't normally browse websites written in a language I can't understand.
1. The link text in the example I provided was in English.
2. I am not aware of any requirement that only one language may be used on a given website. If there is such a requirement, please inform my contacts on Facebook of this, because they post messages there in about 15 different languages using at least 4 different writing systems. (And I've posted there myself in 4 languages, including English.)
I still see an ignorant american that thinks the whole world should read and write english for people like dhermann.
1. See above.
2. So you are saying that you can read my mind? Perhaps this ability of yours needs some fine-tu
terrorist level domain (Score:4, Funny)
Re: (Score:3, Informative)
That has been possible for years.
This is about registering bankofamerica.cõm or lloydstsb.cø.ûk
The part AFTER the dot.
I took Latin in high school (Score:2, Funny)
I'm glad we're going with Non-Latin TLDs now, I never understood going to the website "e.pluribus.unm"
Perdire (Score:3, Funny)
first urls, then slashdot (Score:5, Funny)
ï höpé thãt slâshðõt wìll dö thís töø wìth ÜRLs!
www.íçáñn.örg
ìt wörkéð!
Re:first urls, then slashdot (Score:5, Funny)
Here's a demonstration of how non-Latin characters show on /., starting with Arabic:
Hindi:
Russian:
Japanese:
Korean:
Chinese:
Parent
Re: (Score:3, Insightful)
Just because the characters don't show up in the edited text doesn't mean that they won't be handled in anchor tags or Slashdot's URL tag.
Well, Slashdot mangles them anyway [russian-]. The URL should end in .com.
Slashdot's web interface is quite embarrassing in this respect. Having a non-Unicode-capable page in 2009 is like having one that is optimized for Netscape 0.9, no matter what amount of JavaScript and Web 2.0 bling they put in there.
If international URLs will finally force Slashdot to implement a triviality such as string parsing, so much the better.
ICANN has lost it! (Score:4, Insightful)
Far too much software makes the assumption that TLDs only contain [a-z0-9-], so if you want to go changing that there needs to be a damn good reason, there is not. There are ~1369 2 letter TLDS to be shared between ~200 soverin states and 49284 3 letter generic ones to be split between uses (.xxx .nws .org .edu, etc), there doesn't seam to be any good reason to expand that and make lots of software more complex.
And the answer to that... (Score:5, Interesting)
... of course, is Punycode.
A comment [slashdot.org] before yours has www.íçáñn.örg, which, when entered into Firefox, turns into
www.xn--n-tfarxw.xn--rg-eka
. Looks like the software will still live :)
Parent
Re:And the answer to that... (Score:5, Informative)
You don't understand. Punycode is how second-level domains are already implemented, even on top of relatively old browsers. This is an extension of Punycode to be usable in the TLD as well.
In other words, your current version of Firefox will be able to visit pages in IDN TLDs when they're implemented, and so if someone does create a .örg TLD today, you can go to www.anysite.örg to your heart's content already.
Note that this doesn't mean you can go to www.anysite.örg in NCSA Mosaic or anything, because these old browsers were around when Punycode wasn't even a standard. You can go to www.anysite.xn--rg-eka and NCSA Mosaic will recognise that, though. The seamless IDN TLD usage is just going to be present in the more modern browsers. I expect that Opera 8+, IE 6+, Firefox 2+ and recent Safari/Konqueror/Epiphany are going to be able to visit www.anysite.örg and 'hide' the xn--etc- access details from you, the user.
Happy surfing!
Parent
Re: (Score:2, Informative)
Re: (Score:2)
Though TBH I'm not certain WHY we need TLDs anyways. It isn't like there is some commercial slashdot.com it just redirects. I imagine that any big name will
Re: (Score:3, Insightful)
Yeah right. Because everybody in the whole world only uses ASCII right?
Sorry for sounding flippant, but such US-myopia is far to prevalent for my liking.... Come on guys: Wake up and smell the coffee! There is more to the world than the US! There is no reason to make most of South East Asia and China 2nd-rate citizens on the internet.
I agree that there is a lot of software that needs changing as a result though. But that just means more work, right? You could probably sell this as an anti-recession measure
Re: (Score:3, Insightful)
You know, except for ease of use for those who don't use Latin characters in their daily lives. But who cares about them? They should just go back to their own country and create their own internet.
Re: (Score:3, Informative)
if you want to go changing that there needs to be a damn good reason
I don't have any first-hand experience, but according to the BBC story when one enters a native-script domain name into one's browser, the domain name is entered normally (for the locale) and then to enter, e.g., ".in", one needs to press a key combination to shift the keyboard into latin-mode, then, enter the two letters, then shift the keyboard back into native mode.
It's a usability problem. I sure would be annoyed if .com had to be rend
Re: (Score:3, Funny)
And now, with today's progress, that'd be CØBÖL.
Encoding? (Score:2, Interesting)
The encoding seems weird to me:
Any DNS gurus care to explain why they wouldn't simply use UTF8?
Re:Encoding? (Score:4, Informative)
Parent
Re:Encoding? (Score:5, Informative)
To avoid breaking all the DNS-related code out there that assumes (ie correctly, based on the current spec) only alphanumerics and '-' in each component.
If you wish to rewrite every single bit of DNS-dependent code, in every laptop, server, embedded network device, etc, etc, ... well assume that it can't be done, and with this mechanism it doesn't need to be. Though I bet a few bits of code will barf at the '--' anyhow...
Rgds
Damon
Parent
Re: (Score:2, Informative)
I am not DNS guru, but guessing. RFC882 - November 1983. RFC2044 - October 1996.
Re: (Score:2)
Backwards compatibility with existing systems that don't support UTF-8 but still need to make DNS queries. Ranges from basic tools like dig, to un-updated browsers, to embedded devices like routers.
Are there any public DNS servers that support this to see what happens with my existing software??
Re: (Score:2)
Since software makes the assumption that TLDs only contain [a-z0-9-] [slashdot.org], UTF-8 can't be used in the DNS. Internationalised domain names, even before these new ccTLDs, used that xn-- system, called Punycode [wikipedia.org]. For instance, the site tinyarro.ws, which provides short URLs via a Unicode domain name, already used .ws for that purpose. It turns into xn--hgi.ws when the DNS request is issued.
ccTLDs using Punycode is just an extension of that mechanism for second-level domains.
Erratum (Score:2)
Yeah, Slashdot apparently needs to be internationalised too. That ".ws" should be "[U+27A1].ws" (BLACK RIGHTWARDS ARROW).
Re: (Score:3, Insightful)
Actually, UTF-8 can and is being used in DNS - as long as you stick to basic Latin characters, that is. Also it is Unicode - as I posted earlier, Unicode is a blanket for UTF-8, UTF-16 and UTF-32 which makes it ambiguous.
UTF-8 bits 0-7 is ASCII as long as bit 8 isn't set, so to fully support it you'd need to still exclude bits below 7 that are not valid html characters and include support for multiple bytes and bit 8. The reason existing DNS servers won't work with it is because bit 8 indicates multibyte
Re: (Score:2)
Good question. The field size for DNS requests is in double words (16bits) increments, so I don't see why it couldn't have been.
Re: (Score:2)
Phishing aid (Score:5, Insightful)
don't forget who wer're talking about here... (Score:5, Insightful)
There are letters in the Cyrillic alphabet that have different character codes than their look-alike letters in the Latin alphabet. I'm sure there are other collisions as well. I'm sure they accounted for this in the proposal, but the problem always lies in the implementation
This is a decision made by ICANN. We've known for some time that they will willingly approve really tremendously bad ideas, if enough money is presented to them. They recently moved on a motion to start selling gTLDs, after all.
From a security standpoint, this is a VERY bad idea without proper regulation of domain name registrations, and so far it has been demonstrated that we cannot manage them properly even with only the Latin alphabet
Security is not of any concern for ICANN. Never has been, never will be. As long as they keep making money they're happy; security, spam, phishing, etc, be damned.
Parent
Re:Phishing aid (Score:4, Informative)
I think the limitation that nationalized character sets will be restricted to the country TLDs where that language is native is a good first step. Additionally, I believe you're not allowed to use the latin alternative form characters from unicode (like 0xFF20-0xFF5F).
If you're really paranoid, you could just be extra suspicious of domains that end in two letters (and yes, I am including .us), particularly when the 2nd level name is something you recognize, like paypal, ebay, etc. If you're in China, there may indeed be a legitimate paypal.cn, but I suspect it would set off my spidey sense to see a URL like that show up in my e-mail.
Parent
Re: (Score:3, Insightful)
If you're really paranoid, you could just be extra suspicious of domains that end in two letters (and yes, I am including .us), particularly when the 2nd level name is something you recognize, like paypal, ebay, etc. If you're in China, there may indeed be a legitimate paypal.cn, but I suspect it would set off my spidey sense to see a URL like that show up in my e-mail.
That won't work. There really are a lot of big companies that have country-specific sites that use the two-letter global domains. For example, if you're after books in German then you might be very interested in visiting amazon.de, which is totally legit.
Re: (Score:3, Insightful)
Yeah, but if you know that you want that, then you'll be expecting it. We're talking about being on the lookout for 2 letter TLDs in places you don't expect them.
Re:Phishing aid (Score:5, Insightful)
This risk can be greatly reduced if they limit domain names to only one alphabet, i.e. Russian domain with Cyrillic ccTLD should have only Cyrillic letters in it.
In many of these countries, they often have two domain names for a website: one that is easy to remember by foreigners, one that is easy to remember by locals (i.e. cyrillic name transliterated to Latin alphabet). The transliterated domain name is usually horrible, sounds weird, and often people transliterate stuff in different ways, so it's often not easy to remember anyway.
I think non-latin ccTLDs is a good thing.
matt
Parent
Here comes the Phishers! (Score:2, Insightful)
I'm all for internationalization, but perhaps limit it to internationalized domain extensions (.jp or
Re: (Score:3, Informative)
If ICANN did not standardise this then nations will just implement their own systems which will be different and incompatible with each other, much like China and Thailand have already done.
Are we going to have to update the URL RFC? (Score:2)
Thee current RFC 1738 http://www.faqs.org/rfcs/rfc1738.html [faqs.org] Only allows URLs to be composed of
" Within those parts, an octet may be represented by the chararacter which has that octet as its code within the US-ASCII [20] coded character set. In addition, octets may be encoded by a character triplet consisting of the character "%" followed by the two hexadecimal digits (from "0123456789ABCDEF") which forming the hexadecimal value of the octet. (The characters "abcdef" may also be used in hexadecimal encod
Excellent idea (Score:4, Insightful)
Now those countries, organizations and businesses that wish to become inaccessible to most of the world (except the native speakers of their own language) can finally do so as easily as possible. Create their own little Internet reservations and stay there :)
As long as my software (such as Firefox) obligingly converts these IDN urls into the dash-hex notation making them obviously unreadable, I am ok with that.
Disclaimer: I am a native of non-English speaking country. I am sure a few of my countrymen will use this feature based on misplaced patriotism. I am also sure that vast majority will ignore it just like they ignore potential to use non-latin domain names that exists right now.
Latin =/= Support for English only. (Score:3, Insightful)
Re: (Score:3, Insightful)
Actually we are talking about the English alphabet, with j, u and w, which Latin din't have.
it just got easier to phish (Score:4, Informative)
Yay. Now you can can register yourbankname.com with some funky characters that render in exactly the same way as the letter you are used to.
Re: (Score:2, Insightful)
I wonder what impact this will have on the ever decreasing amount of IPv4 addresses available.
This will have absolutely no effect on IPv4/IPv6. This is a DNS change to allow additional characters in domain names.
The domain names get translated to ip addresses by DNS servers.
I doubt that individuals & companies said, "No! We refuse to go on the internet until we can have TLDs with non-Latin characters."
Re: (Score:3, Informative)
It's already been in use for the rest of the domain name under certain TLDs for some time.
Re: (Score:3, Funny)
Re:Its to do with people with the wrong keyboard . (Score:4, Informative)
How exactly do you think you'll be able to type in a URL in mandarin or russian on west european keyboard?
You enable Chinese keyboard layout (dunno what's it called), and type it. The letters printed on the keys of your keyboard aren't some sort of magic that lets your computer input languages written in them, you know.
I don't have any keyboards with Russian characters on them, but I happily type in Russian regardless (in fact, I only first realized that I do actually truly touch type when I first ran into this problem, which turned out to not be a problem in the end).
Parent
Re: (Score:3, Interesting)
I'm happy you'll do this. I won't, and the majority of the internet users won't either. It'll just further separate nations, because I won't go through the hassle of typing in a foreign character domain name - it'll just a site I won't visit.
Presumably, if a site is designed to be visited by someone who only understands English, it will use an English TLD. If it uses TLD with national characters, then most likely the content is in the language other than English as well, and you'd need to have means to input that language to fully interact with the site anyway.
Re: (Score:3, Insightful)
"the majority of the internet users won't either."
Sorry, but that sounds like typical American ethnocentricity. The MAJORITY of internet users actually are people who don't natively speak English. Chinese speakers, Russian speakers, European people, many of whom use cyrilic alphabets, Arabs, South Americans, Indians, and others that I'm surely missing.
How can you possibly speak for "the majority of internet users", when people who speak English as their native language constitute a pretty small percentage
Re:Its to do with people with the wrong keyboard . (Score:4, Insightful)
Uh, yeah, because the keyboard you're using is a clear indicator of which language(s) you understand.
Parent
The Internet has to evolve (Score:5, Funny)
....although obviously not ... in Kansas.
Parent
Re: (Score:3, Funny)
micrösöft.cöm?
That's Microsoft with the volume turned up to 11?
Re: (Score:3, Informative)
Several mistakes there.
First of all any domain name is going to have to be encoded as a stream of bytes somehow because far too much stuff is already implemented to handle the string that way. As others pointed out punycode is used.
Second, UTF-8 is smaller than UTF-16 for all languages, even Chinese. This is because all the ASCII 0x00-0x7F characters are smaller, and therefore the encoding will be smaller if there are more of these than there Unicode 0x800-0xFFFF characters. This seems incorrect for Chinese
Re: (Score:3, Insightful)
I don't normally browse websites written in a language I can't understand.
1. The link text in the example I provided was in English.
2. I am not aware of any requirement that only one language may be used on a given website. If there is such a requirement, please inform my contacts on Facebook of this, because they post messages there in about 15 different languages using at least 4 different writing systems. (And I've posted there myself in 4 languages, including English.)
I still see an ignorant american that thinks the whole world should read and write english for people like dhermann.
1. See above.
2. So you are saying that you can read my mind? Perhaps this ability of yours needs some fine-tu