Technical Notes |
Version | 3 |
Author | Ken Lunde 小林劍󠄁 |
Date | 2023-09-12 |
This Version | https://www.unicode.org/notes/tn45/tn45-3.html |
Previous Version | https://www.unicode.org/notes/tn45/tn45-2.html |
Latest Version | https://www.unicode.org/notes/tn45/ |
The Unihan database, as documented in UAX #38, Unicode Han Database (Unihan), has changed with each subsequent version of the Unicode Standard, both in terms of the actual properties that are included, and the number of ideographs that are assigned to each property. The purpose of this Unicode Technical Note is to provide the history of Unihan database properties.
This document is a Unicode Technical Note. Sole responsibility for its contents rests with the author. Publication does not imply any endorsement by the Unicode Consortium.
For information on Unicode Technical Notes, including criteria for acceptance, see Unicode Technical Notes.
The body of this Unicode Technical Note is contained in the three-sheet Excel file “tn45-3.xlsx.”
The Excel file includes a total of 115 published Unihan database properties, ranging from Unicode Version 1.1.5 to 15.1.0. For each version of the Unicode Standard, the coverage of each property is provided, both in terms of the number of ideographs that are assigned to each property and the percentage among all ideographs in that version of the Unicode Standard. Its three sheets include these figures for 1) CJK Unified Ideographs and CJK Compatibility Ideographs (“Unified & Compatibility”); 2) CJK Unified Ideographs only (“Unified”); and 3) CJK Compatibility Ideographs only (“Compatibility”). A blank cell indicates that the property is not included in the corresponding version of the Unicode Standard.
The following summarizes modifications from the previous version of this document:
© 2022–2023 Ken Lunde. This publication is protected by copyright, and permission must be obtained from the author and Unicode, Inc. prior to any reproduction, modification, or other use not permitted by the Terms of Use.
Use of this publication is governed by the Unicode Terms of Use. The authors, contributors, and publishers have taken care in the preparation of this publication, but make no express or implied representation or warranty of any kind and assume no responsibility or liability for errors or omissions or for consequential or incidental damages that may arise therefrom. This publication is provided “AS-IS” without charge as a convenience to users.
Unicode and the Unicode Logo are registered trademarks of Unicode, Inc., in the United States and other countries.