Mapping other Digits to 0-9

Eric Brunner-Williams ebw at abenaki.wabanaki.net
Fri Dec 5 21:18:03 CET 2008



Andrew Sullivan wrote:
> On Fri, Dec 05, 2008 at 11:26:32AM -0800, Shawn Steele wrote:
>
>   
>> That's fine, but then I'm confused about what the discussion of the
>> Arabic digits is?  Is it just to disallow Arabic digits?
>> (Disallowing them implies to me that someone would map them.)  In
>> either case this isn't just Arabic digits, we allow mapping of
>> digits for other scripts as well.
>>     
>
> No, I believe what we are discussing is adding a context rule to the
> protocol that says, "If a label contains a code point in $somerange,
> it must not also contain any code point for $otherrange."  The
> discussion is (1) whether to add this at all and (2) if adding it is
> ok, what the values of $somerange and $otherrange should be.
>   

Yup. For instance, as an example I'm in no way suggesting is correct:

"If a label contains a code point in $somerange, then it may not contain 
any code points not in $somerange" (source: Draft Applicant Guidebook: 
Module 2 Evaluation Procedures,  Section 2.1.1.3.2 String Requirements, 
page 2-8, bullet #5, ICANN, 2008)

In that particular formulation, $somerange is somewhat larger than 10, 
but this example would apply to a label with a code point in the "Latin 
Script digit" range and a code point in either of the "Arabic Script 
Block" sets of digits.

Naturally, I'm not suggesting this example is informative on the 
question, as it is both a draft proposal, and incorrect on a larger 
question than the presence of code points representing digits in a 
particular kind of label. But it is an example of this class of rules 
we're considering.

Eric




More information about the Idna-update mailing list