- From: Jony Rosenne <rosennej@qsm.co.il>
- Date: Sat, 19 Feb 2005 18:59:49 +0200
- To: <www-international@w3.org>
> -----Original Message----- > From: www-international-request@w3.org > [mailto:www-international-request@w3.org] On Behalf Of Martin Duerst > Sent: Saturday, February 19, 2005 3:44 AM > To: Jony Rosenne; www-international@w3.org > Subject: RE: IDN - RTL > > > > At 00:00 05/02/19, Jony Rosenne wrote: > >So this type of string should be avoided - but the > restriction should be > >minimal, and strings that do not cause a problem should be allowed. > > Hello Jony, > > I think we all agree that from an user point of view, it would > have been desirable to allow numbers at the end of RTL labels. > > However, the restrictions we were working with were the following: > - Avoid as much as possible the chance that domain names get > displayed in a confusing way. (see Mati's example) > - Express the restrictions in terms of single labels, not > dependent on the rest of the domain name. It seems the difficulty stems from this rule > - Express the restrictions in a simple, easy to implement, way. > > If you have a good idea of how to address the above restrictions > in a different way than it is done now, allowing more domain > names, please tell us. Probably the only solutions are either to relax the second rule, or to accept ambiguities as per Mati's example and advise those registrars that wish to support bidi IDNs that they ought to control some particular cases. Is the restriction only on Arabic (commonly known as European) digits, or does it include also Hindi (commonly known as Arabic) digits? Jony > > Please note that the same restrictions apply to IRIs, altough > the spec is less strong (SHOULD rather than MUST) in that case, > to take into account that many components in an IRI are just > data and rarely are read/typed by the user. > > Regards, Martin. > > > >
Received on Saturday, 19 February 2005 17:01:11 UTC