So if i understand you correctly you are saying:
- A user buys a computer in Moscow and the default setting is Russian...
He types in ÐоÑква.ком to his browser and gets to the site (But he is actually visiting Moscow.com)?
Yes (and no), if that is the proper spelling and characters.
.ком itself will not be a registrable domain extension as it is a
translation of .com
Now, if someone already has ÐоÑква.com (which they do) then they have a great domain - a dual purpose.
Where the problem comes in is - in the not-so-distant future - is when browsers come in and auto translate every thing as the user sets the defaults.
Inevitably, and I have seen examples, a browser can be set to a default language, just like a keyboard, by the user.
There was some experimentation with Google translation and I think someone here even posted examples just a week or so ago.
It is still further down the road but at the pace of technology these days, I can not see this as being that far off. Firefox is also behind this.
What one viewer sees in Russian script (because he set his browser to Russian) I will see the exact same site in English (because I set my browser to English) and perhaps Acro will want to see the sites he visits in Greek (because he set the default to Greek).
There will be nothing else to key in or press or Translate button as this is all set per the browser.
So we now have three people viewing the same page in three different languages and all we had to do was set the browser as such.
-------------------
The biggest issue I see here has been ICANN dragging their feet and having taken so long to roll out IDN that technology has caught up to them.
When a browser is capable of translating every word, then what is the need for IDN specifics?
When a person is capable of using their keyboard to enter
their chosen language into the browser window and get to the site that renders everything in
their chosen browser default, the what is the need for IDN?
That is the biggest issue I see.
ICANN dragging their feet at least a decade on this IDN issue to where shortly after it is adopted, IDN runs the risks of becoming un-necessary.
---------------------------
Now, remember my Yes (and no) answer?
This is where the real confusion comes in and something ICANN is going to have to deal with.
When browsers do have this capability, what will be correct? Moscow.com or ÐоÑква.com? Remember, ÐоÑква.com
AND Moscow.com already exist. One goes to Moscow.com and the other goes to
http://xn--80adxhks.com/
Now, here comes IDN.
What are we going to end up with?
Moscow.com
ÐоÑква.com
ÐоÑква.ком