On 24 Jul 2010, at 20:34, karl williamson wrote: > What would the problems be of having a stability policy in regards to > assigning characters to have numeric type = decimal, something like the > following: > > "New scripts or forms (like mathematical mono space) that have decimal > numbers will be assigned so that those decimal numbers occupy at least 10 > contiguous code points such that the code point for DIGIT ONE = 1 + the code > point for DIGIT ZERO, etc.
This just isn't going to happen. We may do it, but there isn't going to be a "policy" formed about it. > This would help my implementation of converting strings into numbers while > not allowing mixed scripts (or forms) in them. I believe that the current > data follows this policy. It would be nice if it were made explicit. U+19DA > (NEW TAI LUE THAM DIGIT ONE) is the one current case where there is more than > one digit with the same meaning in a script or form. I presume this is an > anomaly that is not likely to be repeated, but would have been accommodated > by the above policy. I presume it was just lucky that when this character > came to light there was an unassigned code point available just after the > DIGIT NINE. Digits can be scattered randomly about the code space and it wouldn't make any difference. Michael Everson * http://www.evertype.com/
