From: Jill.Ramonsky@Aculab.com
Date: Tue Aug 19 2003 - 05:09:46 EDT
Thanks, but not good enough.
What guarantee do I have that other Unicode characters will not be added in
the future which have the property "Hex_Digit"?
How do I write an algorithm which will convert Unicode hex characters to
hexadecimal which is guaranteed to work for all future versions of Unicode?
(The algorithm is allowed to read the machine-readable charts, which may
obviously be replaced with updated versions as they arise).
Jill
-----Original Message-----
From: John Cowan [mailto:jcowan@reutershealth.com]
Sent: Monday, August 18, 2003 4:39 PM
To: Jill.Ramonsky@Aculab.com
Cc: unicode@unicode.org
Subject: Re: Clones (was RE: Hexadecimal)
> Secondly, I believe that the code charts SHOULD provide machine-readable
> information about the hexadecimal values of the letters "A" to "F".
0030;0
0031;1
0032;2
0033;3
0034;4
0035;5
0036;6
0037;7
0038;8
0039;9
0041;10
0042;11
0043;12
0044;13
0045;14
0046;15
0061;10
0062;11
0063;12
0064;13
0065;14
0066;15
FF10;0
FF11;1
FF12;2
FF13;3
FF14;4
FF15;5
FF16;6
FF17;7
FF18;8
FF19;9
FF21;10
FF22;11
FF23;12
FF24;13
FF25;14
FF26;15
FF41;10
FF42;11
FF43;12
FF44;13
FF45;14
FF46;15
Thuryago.
This archive was generated by hypermail 2.1.5 : Tue Aug 19 2003 - 06:00:43 EDT