DryHeat said:
[*]Are you already, or planning to get, into IDNs?
Have about 100 IDNs and buying more all the time.
DryHeat said:
[*]Do you feel that from a practical standpoint, a pure English-only domainer can make intelligent speculative investments in IDNs?
It's possible, but one needs to be very careful of definitions ... some languages have multiple spellings / symbols for the same word due to gender, usage, etc. Google's translation tool and similar leave much to be desired - many definitions don't reflect real-world usage and/or are ambiguous.
DryHeat said:
[*]What are the chances that like many other MS products in the past IE7 has significant issues in regards to IDNs and a reverse-decision is made to drop them?
IDNs are here to stay, but with
significant restrictions in how they will be treated by various applications, in particular web browsers.
For example, an IDN that contains characters from multiple character sets (ie. English and Russian) are subject to being highlighted / blocked; IDNs are now required to have a language tag ... those that have invalid tags may at some point may be subject to being deregistered in some limited instances - with that said, there are various legitimate reasons for mixing languages, but again to be clear, most software, such as MSIE 7, will highlight / block them by default.
DryHeat said:
[*]What is the realistic aftermarket potential for such investments? I think this is very relevant since despite some sales here and there so far we have not seen any significant/consistent aftermarket events for either .cn or .in. , the two prime candidate countries for IDNs.
I view IDNs, even in .COM, as being more like glorified ccTLDs ... thus as a group will have limited value compared to traditional A-Z only domains, especially in .COM.
I'm running into a lot of issues that many IDN folks aren't discussing - probably because they've not consider them ...
Various issues / threats / questions:
?? The existance of numerous diverse dialects, even totally different languages, etc in the same country ... it's among the reasons that English dominates in some areas; some natives, even if they can understand a particular dialect, will sometimes speak a totally non-native language, such as English, instead to avoid risk of offending the other party. One can't assume one language dominates an entire region - languages can also overlap many areas ... it's one of the reasons some are pushing for language / culture based TLDs, such as .CAT (among the dumbest ideas ever, but that's another discussion for the .CAT thread running here on DNF).
?? An IDN that contains western european characters that very close matches a non IDN ... ie.
cafe.com verses
café.com ... what happens? Will the IDN be highlighted / blocked by default? ... likely an easy UDRP target? ... introduction of a new IDN specific dispute procedure? -perhaps there already is one?
?? Trademark issues ... ie. an IDN that is similar / exact to a trademark in another country ... less obvious, what about an IDN that translates to that of a trademarked word / phrase? -I believe there's a thread discussing such an issue now on one of the other boards here.
?? language variants (more applicable to asian languages, etc) related issues ... how good / stable are the various language variant tables?
?? what happens when a language variant table changes? -how are conflicts handled?
?? what happens if a character variant (an IDN [IDL package] technically can comprise multiple character variants [code points]) is released? ... does the current registrant get first dibs? ... even if yes, it may not be quite that simple if a character variant occurs in numerous permutations.
?? What happens if a reserved character variant is changed to a preferred character variant? - while such a change would have little to no effect on affected IDNs (IDL packages), it could result in the appearance of some IDNs changing ... probably not a biggie compared to some other issues, but one to be aware of.
?? How reliable, especially for those in languages with numerous character variants, will IDN domain resolution be? ... IDN resolution depends on much client-side APIs.
?? How well will IDN resolution APIs be regulated ... I can easily envision scenerios in which a web browser and/or other applications (email, IM, etc) implement resolution differently ... ie. adding and/or ignoring one or more valid language associations for a particular IDN / converting similar-looking western european characters to standard A-Z characters, etc. A related concern is language table management - I'm a little hazy on if the tables will be internally stored by each app or remotely loaded for each session, etc.
Rambling on, but there are a lot of things that one needs to be aware of with IDNs.
DryHeat said:
[*]Are there reliable tools for an English-only domainer to use to speculate in IDNs, and if so where?
I've not seen any. With that said, there are some IDN specific message boards out there that have many members who specialize in IDNs, and are in the process of developing / refining various IDN related tools.
DryHeat said:
I hope we could get some useful and informative posts here in this thread to educate those of us who have not yet wet our feet with IDNs to decide once and for all whether this is our cup of tea or not?
IDNs are definitely worth considering ... but, in my view, don't bet the ranch on them. IDNs are best suited for applications in which a standard A-Z domain is far less than ideal, such as for Chinese and Japanese domains. In contrast, western european IDNs are a potential minefield; have limited value.
A lot of information ... hope this helps.
Ron