mktables: A leading zero is different than an only 0
authorKarl Williamson <public@khwilliamson.com>
Sun, 11 Mar 2012 22:46:18 +0000 (16:46 -0600)
committerKarl Williamson <public@khwilliamson.com>
Mon, 19 Mar 2012 22:51:25 +0000 (16:51 -0600)
commit6342d44542ab62d41255e7655319b5f5ce0975a3
tree2414615ab976064056c284006eada18d1a3af766
parentb577d4a6d9513ee5434c94e3104462fdd700d6a7
mktables: A leading zero is different than an only 0

Commit b91749bce0ff3d86c6e210a0b35289b4ad36c144 assumed that a single
0 was a leading 0.  This inappropriately makes a table appear to be hex
when it isn't.  This currently affects the kPrimaryNumeric property
which is part of the Unihan database, and is not normally generated by
mktables; it is generated only if an installation decides they want
to compile Perl to use the Unihan properties.
lib/unicore/mktables