>
>
> > How many different keyboards and different fonts will I need to add
> > Multilingual Domains into DNS if it ever works with bind? I'm already
> > receiving inquiries that look like this "¤j²z¥Û³J¿:" if I buy all the
> > different keyboards and language cds from Microsoft, do you have to set
> > up parallel versions of opensrs to customize the instructions for users
>
> I have no answer for the above...
The RACE converter handles all that end of it, as will/does the UTF-8 tools.
Windows 2K appears to handle all the languages required, built righ in. If
not loaded by default, you set them up from the install disks. I've got
Chinese (both sets) Japanese and Korean as well as English installed here
right off the install disks, and the others are available there as well.
Parallel versions of OpenSRS... for each language. Possibly that's one way.
It might depend on whether you are going to offer all languages... in which
case you may need to employ multilingual staff to handle queries. Like
"¤j²z¥Û³J¿:"... :-) which would resolve to the correct font if you had it
installed on Win or Mac etc.
Installing parallel versions of Opensrs code isn't all that difficult
anyway. Once one is running, the rest are exactly the same except for the
templates and languages displayed.
Add a rider that all communication from the Opensrs site itself is in
English, and have a link to bablefish or one of the other translation
servers, or install the translation software software on your own server.
In short - it will depend on your committment. If you are going to offer the
MLDNs as an add-on to other services, and hope to make zillions. It may not
be worth the work.
>
> > and handle all the different credit and exchange rates?
>
> Why? The credit card system already does this.
and WorldPay.com even does it in any language you like, and any currency you
like.
>
> > Will I be able to customize the domain registered reply email to the
> > clients language?
>
> No, I don't think so.
I rekon this will change with demand. Not difficult to impliment, based on
some "bit" sent along with the registration code. Even the attached encoding
type. If encoding=ja, then remply in Japanese. piece of cake. youhoo,
Opensrs developers?????
>
> > Has anyone that's registered one get it to resolve?
>
> They don't work. It's just a way for Verisign to increase their revenue
> due to the decrease in registrations at Network solutions. It makes their
> shareholders happy in the short term. However they are going to have
> bigger problems when customers start complaining (...and filing lawsuits)
> that they are being sold a bunch of hot air...
taht's on the cards - so be very careful what you promise clients. You
should TELL them they are just place markers and purely experimental for
now. However, having said that, developments are proceeding apace and domain
resolution is being developed by the bodies who manage that. It's finally
dawned on the developers that a lot of people don't speak English... and
still want to use the Internet. and having said that - I would hazard a
guess that it's still at least two years away from full operability. (and
that's nothing to do with the star of the day time chat show!)
those with the bits in place will be the early players. The rest will be in
the scramble to climb on the hayride.
cheers
Robert
