Maintained by the HKIUG Unicode Task Force

Revision History

• Version 1.0. Released on 16 September 2003
• Version 1.0.1. Released on 20 January 2005
  (1) Changed 21606A to map to U+98F2, instead of mapping to U+98EE
• Version 1.0.2. Released on 12 August 2005
  (1) Changed 23355C to map to U+8C63, instead of incorrectly mapping to U+86C3
  (2) Removed 3B3555 to avoid creating a multi-mapping case due to the change in (1) above
• Version 1.0.3. Released on 11 November 2008
  (1) Added 37 entries of Bopomofo characters (ranging from U+3105 to U+3129)
• Version 1.0.4. Released on 20 April 2011
  (1) Added 9 entries - they each have same EACC but different Unicode with an existing entry. These 9 pairs of entries are marked with the note: "multi-mapping to-eacc".
• Version 1.0.5. Released on 14 November 2013
  (1) Added 23 characters that have Unicode code point but do not have an EACC/CCCII eqivalent. 23 new 7Fxxxx code points were created to hold these characters in the EACC/CCCII column.

Table Columns

• EACC/CCCII Column - Code value of EACC or CCCII
• Unicode Column - Unicode value
• Glyph Column - the glyph of the Unicode value as displayed in your browser
• Remarks Column
  (1) Describe whether the code value in the first column is an EACC or a pure CCCII. Pure CCCII means the code value appears only in the CCCII standard but not in the EACC standard, and its existence in this table will not cause multiple mapping.
  (2) multi-mapping linked means the entry belongs to a case of multiple mapping in which the EACC/CCCII code values of the entries are linked (i.e. the two low-order bytes are the same).
  (3) multi-mapping unlinked means the entry belongs to a case of multiple mapping in which the EACC/CCCII code values of the entries are not linked (i.e. the two low-order bytes are not the same).
  (4) HKIUG preferred means the entry is the HKIUG preferred mapping in a mulit-mapping unlinked case.