Is this the best is ever going to get? I mean, those of you who really understand the problem with multilingual DNS resolving (I must admit I am pretty lost by now), do you think there will ever be a "full" solution to this. Something that works in most browsers, with or without protocol and without having to installa any odd plugin?
There is no need to say that from my point of view someone should sue Verisign for putting on the market a product that does not really work. This is exactly the same (or worse) than all this new fake TLDs that work if you install this or that. At least they admit it from the beginning but I was very convinced at the time, that Multilingual domaiins were based on the fact that would become as standart as the rest of ICANN TLDs and would operate in most default configurations. If they can not archieve this then they could return all the money received from this completely unuseful domains. Writing a "handbook" to my clients on how to input my address in their web browser it's not exactly my idea of "operational". It apparently all comes down to Versign again.. god save us. Jose Luis > From: "Ken Joy" <[EMAIL PROTECTED]> > Date: Wed, 6 Mar 2002 11:44:24 -0500 > To: "Sergei Kolodka" <[EMAIL PROTECTED]>, "\(John Spohr\)" > <[EMAIL PROTECTED]> > Cc: "'Sergei Kolodka'" <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]> > Subject: RE: Multilingual domains > > For the record, I was certainly not familiar with these issues to the depths > that Sergei has explained them. I shall investigating a little further and > adding these notes to our docs, thanks! > >> attractive. I >> JS> mean what are people paying money for? >> >> JS> Still think we will lose 90% of our registrants if something real >> JS> doesn't happen. > >> Well, as i remember, it work seamless if you have installed >> client from i-DNS, i believe that even hyperlinks must work. >> Again, it works only for those who know about that client, and >> you or someone else must tell them about this client... > > These are the issues that I want to investigate before adding new > information to the docs. > > Thanks, > > Ken > >> >> -- >> Best regards, >> Sergei Kolodka >> [EMAIL PROTECTED] >> >> >> JS> Still think that Verisign should be convinced not to charge until they >> JS> actually work so that Tucows won't have to either. >> >> JS> A million thanks Sergei. >> >> JS> John R. Spohr >> JS> I.S. International, Inc. >> JS> Tokyo, Japan >> >> JS> -----Original Message----- >> JS> From: [EMAIL PROTECTED] >> JS> [mailto:[EMAIL PROTECTED]] On Behalf Of Sergei Kolodka >> JS> Sent: Wednesday, March 06, 2002 1:40 AM >> JS> To: [EMAIL PROTECTED] >> JS> Subject: Re[4]: Multilingual domains >> >> JS> Hello Ken, >> >> >> KJ>> That will depend on whether the DNS is set up with a hostname (www) >> JS> or not, >> KJ>> wouldn't it? >> >> JS> No, it is not. >> >> JS> Let's say we have domain in chinese whatever-in-chinese.com, >> JS> it's UTF8 representation (HJ5kj5kj5.com) and RACE >> JS> encoded representation (bq-xxx.com). >> >> JS> When multilingual domain entered to IE5 _without_ >> JS> protocol part (whatever-in-chinese.com, without http://) >> JS> Explorer send UTF8-encoded domain (HJ5kj5kj5.com) to >> JS> auto.search.msn.com and then correct (bq-xxx.mltbd.com) >> JS> address came back to browser from microsoft's >> JS> search engine together with redirect to bq-xxx.mltbd.com. >> JS> So multilingual address work and we can reach >> JS> requested page. >> >> JS> If multilingual domain entered _with_ protocol part of >> JS> URL (http://whatever-in-chinese.com), address treated >> JS> as usual domain and explorer tries to do search for >> JS> UTF8 representation of this domain (HJ5kj5kj5.com.com) >> JS> in real DNS database, can't find it there and fail with >> JS> DNS error message. >> >> >> JS> -- >> JS> Best regards, >> JS> Sergei Kolodka >> JS> [EMAIL PROTECTED] >> >> >> KJ>> ie. >> >> KJ>> multilingual.mltbd.com IN A IP.ADD.RE.SS >> >> KJ>> vs. >> >> KJ>> www.multilingual.mltbd.com IN A IP.ADD.RE.SS >> >> KJ>> Ken >> >>>>> -----Original Message----- >>>>> From: [EMAIL PROTECTED] >>>>> [mailto:[EMAIL PROTECTED]]On Behalf Of Sergei Kolodka >>>>> Sent: Tuesday, March 05, 2002 10:40 AM >>>>> To: [EMAIL PROTECTED] >>>>> Subject: Re[2]: Multilingual domains >>>>> >>>>> >>>>> Hello Ken, >>>>> >>>>> >>>>> KJ> Once that's done, web surfers with IE 5 or greater who enter >> JS> native >>>>> KJ> characters into the URL window and hit 'enter' will be taken >>>>> to the site >>>>> KJ> specified in the DNS> >>>>> >>>>> >>>>> Just one addition (it's very common mistake >>>>> between our multilingual domains users). >>>>> >>>>> You MUST enter in browser something like >>>>> www.multilingual.com or multilingual.com. >>>>> but NOT http://multilingual.com or >>>>> http://www.multilingual.com. >>>>> >>>>> -- >>>>> Best regards, >>>>> Sergei Kolodka >>>>> [EMAIL PROTECTED] >>>>> >> >> >> JS> -----Original Message----- >> JS> From: [EMAIL PROTECTED] >> JS> [mailto:[EMAIL PROTECTED]] On Behalf Of Sergei Kolodka >> JS> Sent: Wednesday, March 06, 2002 1:52 AM >> JS> To: Ken Joy >> JS> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] >> JS> Subject: Re[2]: Multilingual domains >> >> JS> Hello, >> >> JS> Try www.$B%H%J!<(B.com - WITHOUT leading http:// >> >> JS> Multilinguals work only this way and only in >= IE5. >> >> JS> And you can't click on link, because you need to >> JS> use http:// in URL or browser will treat URL as >> JS> local link. >> >> JS> -- >> JS> Best regards, >> JS> Sergei Kolodka >> JS> [EMAIL PROTECTED] >> >> >> >>>>> I have just tried this again from all of the above 98J IE5 does not >>>>> Resolve, Win2000ServerJ IE5.5 does not resolve, WinXPJ IE6 does >> JS> not >>>>> resolve and when you type http://www.$B%H%J!<(B.com$B!!(Binto any >> JS> of >> KJ>> the above >>>>> browsers and combinations they do not work or resolve. It also does >> JS> not >>>>> work by clicking on the above links. >> > >
