Marco,
I was saying that the locale be part of the name so that I would sign on to:
it_IT,www.���.com
Not only would it localize properly but the request would be routed to the
server handling it_IT names.
If you don't like that then how about www.���.it if you like it in URLese.
All .it names would follow the Italian rules. This should avoid most of the
problems discussed so far.
Carl
-----Original Message-----
From: [email protected] [mailto:[email protected]]
Sent: Wednesday, October 04, 2000 6:05 AM
To: Unicode List
Subject: RE: New Name Registry Using Unicode
Carl W. Brown wrote:
> It would certainly seem that the optimal solution would be to
> carry the locale.
Not at all, and for a good reasons: I need that, whenever and wherever I
type in a certain string, I reach the same web site.
Scenario:
Imagine that I am a customer of ���, a (fictionary) Italian bank.
Imagine that I am used to connect to it through URL "www.���.com" (which, in
Italy, is normalized to the actual address "www.aou.com").
Imagine that, once connected and entered a password, I can perform whatever
operations on my bank account.
Imagine that, while visiting Scandinavia, I want to connect to my bank for a
quick operation, and I use the hotel's computer.
Imagine that I type in my usual "www.���.com", but in Scandinavia, unlike at
home in Italy, this string normalizes to "www.���.com".
Now imagine that someone registers a domain "www.���.com" and built on it a
perfect replica of www.aou.com, with the sole purpose of grabbing passwords
from Italian turists in Scandinavia, to make their bank accounts much
lighter...
Note: if you think that this scenario is too fictionary, you clearly don't
know my fellow country(wo)men!
_ Marco
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:21:14 EDT