From: Mark Davis (mark.davis@jtcsv.com)
Date: Wed Nov 26 2003 - 11:02:48 EST
I agree that it would be best to have a formal policy on that; but we could not assign different numbers without a contradication in the way that number_value and number_type are defined, so the relationship is stable.
Mark
__________________________________
http://www.macchiato.com
► शिष्यादिच्छेत्पराजयम् ◄
----- Original Message -----
From: Arcane Jill
To: unicode@unicode.org
Sent: Wed, 2003 Nov 26 02:12
Subject: RE: numeric properties of Nl characters in the UCD
That is almost precisely what I said. You repeated it perfectly. Thanks.
But actually, there is one small difference between what I said and what you said. I merely observed that no characters have different non-null values for the various number-related properties. But you state (emphasis on *cannot*) that this is guaranteed. Please confirm - is there a hard-coded guarantee that no character will ever be added in the future for which the various number-related properties will have different non-null values? Such a guarantee would be useful, as it would allow me to do more optimisation of stored data.
Jill
> -----Original Message-----
> From: Peter Constable [mailto:petercon@microsoft.com]
> Sent: Tuesday, November 25, 2003 6:04 PM
> To: unicode@unicode.org
> Subject: RE: numeric properties of Nl characters in the UCD
>
>
> Not all characters representing numbers are digits. Not all characters
> representing digits are decimal digits.
>
> What *cannot* happen is for a character to have different non-null
> values for the various number-related properties.
>
This archive was generated by hypermail 2.1.5 : Wed Nov 26 2003 - 11:56:49 EST