RTL & Labels

From IUCG - Internet Users Contributing Group

Jump to: navigation, search

Abdulrahman I. ALGhadir 20091013

while I was reading draft-ietf-idnabis-bidi-06.txt I found this:

“4.3. Strings with numbers

By requiring that the first or last character of a string be category R or AL, RFC 3454 prohibited a string containing right-to-left characters from ending with a number.

Consider the strings ALEF 5 (HEBREW LETTER ALEF + DIGIT FIVE) and 5 ALEF. Displayed in an LTR context, the first one will be displayed from left to right as 5 ALEF (with the 5 being considered right-to- left because of the leading ALEF), while 5 ALEF will be displayed in exactly the same order (5 taking the direction from context). Clearly, only one of those should be permitted as a registered label, but barring them both seems unnecessary.”

Why permitting done on the protocol level ? shouldn’t this be done at registry level?

Ex. If someone wants to register 3COM (COM is a RTL word) registry will register 3COM for him/her and will lock COM3. At least this will give users the choice for picking not forcing them on one type?


Vint Cerf 20091013

for the most part, the IDNA2008 specification does place a great deal of responsibility on the registry but for some cases, it was considered important to bar particularly confusing situations at the protocol level. This was debated substantially during the course of the development of IDNA2008.


Abdulrahman I. ALGhadir 20091014

Well yes it is confusing and yes there are other confusing problems which the protocol simply assign it to registry what I say it is unfair to prevent all domains Which they start with digits to be as choice for user if this problem moved to registry level a registry can simply do:

1) Act same as what the protocol do now (preventing all domains which start with digits).
2) Register domains which start with digits and lock the same domain which end with digits and the opposite.

And any further problems which may result from using 2) can be solved as the registry wants. Plus if the protocol allowed this maybe bidi algorithm will support domains who knows.

Personal tools