|
| Version | 5 |
| Author | Ken Lunde 小林剣 |
| Date | 2026-01-28 |
| This Version | https://www.unicode.org/notes/tn50/tn50-5.html |
| Previous Version | https://www.unicode.org/notes/tn50/tn50-4.html |
| Latest Version | https://www.unicode.org/notes/tn50/ |
The normativekIRG_KPSource (aka KP-source) property, which is documented inUAX #38, Unicode Han Database (Unihan), was introduced inUnicode Version 3.1.1 (2001), and its property values have changed in subsequent versions of the Unicode Standard. The purpose of this Unicode Technical Note is to document the history of changes to this property whose property values correspond to the DPRK character set standards, KPS 9566 and KPS 10721, along with documenting known issues with mappings and representative glyphs. No one outside of DPRK has ever seen the actual KPS standards, so it is useful to document property value changes that have been made to this property. The KPS 9566 character set standard, whosekIRG_KPSource source prefix is KP0, can be glimpsed throughISO-IR-202:1998 (PDF), which is mirrored in the IRG document register as documentIRG N2783.
This document is aUnicode 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, seeUnicode Technical Notes.
The body of this Unicode Technical Note is contained in the single-sheet Excel file “tn50-5.xlsx” and the Description section below.
TheUnified & Compatibility sheet of the Excel file covers a total of 214 code points, one per row and in increasing code-point order, with property values in columns ranging from Unicode Version 3.1.1 (2001) to 17.0.0 (2025). For cases when a particular version of the Unicode Standard exhibited no changes tokIRG_KPSource property values, a range of version numbers is specified for that column. 57 of the code points correspond to CJK Unified Ideographs in theCJK Unified Ideographs (7),Extension A (5),Extension B (35),Extension C (9), andExtension H (1) blocks, and the remaining 157 code points, which are highlighted inblue, correspond to CJK Compatibility Ideographs in theCJK Compatibility Ideographs (107) andCJK Compatibility Ideographs Supplement (50) blocks. Significant changes are highlighted inred andgreen.Red signifies a property value that was removed from the code point in subsequent versions of the Unicode Standard.Green signifies either the new code point for a removed property value or its replacement property value in the case of disunification.
The table below provides details about known suboptimal mappings that covers a total of 42 KP-source ideographs, one per row and in increasing source reference order, all but the first of which use the KP1 (aka KPS 10721) source prefix. While their current mappings are considered suboptimal, it has been deemed prudent to leave the mappings as-is without more information.
| KP-Source | Current | Better | Notes |
|---|---|---|---|
| KP0-CDA9 | U+5609 | U+2B158 | Reported by Michel Mariani via ReportIDID20250929183457 |
| KP1-3413 | U+4E17 | U+2000D | Reported by Judith Chen via PRI #497 ReportIDID20240217105436 |
| KP1-3DB4 | U+217EE | U+5A90 | |
| KP1-3E34 | U+5B76 | U+5B73 | |
| KP1-3EC8 | U+5C12 | U+21B57 | |
| KP1-3EE4 | U+5C35 | U+2BD52 | |
| KP1-3F1C | U+5C6E | U+4DB9 | |
| KP1-44BD | U+2297B | U+2D7E7 | Cognate but no UCV |
| KP1-4850 | U+657B | U+22FCC | |
| KP1-49AC | U+6685 | U+23236 | |
| KP1-4A00 | U+66DA | U+232E1 | |
| KP1-4AD6 | U+23402 | U+233CB | Reported by Michel Mariani via ReportIDID20250929183457 |
| KP1-4D4C | U+3BDE | U+23693 | Reported by Andrew West via PRI #497 ReportIDID20240403090227 |
| KP1-4F56 | U+239F7 | U+2C194 | |
| KP1-5450 | U+702C | N/A | Identical to U+7028 (KP0-DAA4) |
| KP1-5642 | U+24454 | U+2C2D6 | Cognate but no UCV |
| KP1-5653 | U+720B | U+24455 | Reported by Andrew West via PRI #497 ReportIDID20240327155804 |
| KP1-5662 | U+7222 | U+3E0F | Cognate but no UCV |
| KP1-5863 | U+7361 | U+2486F | |
| KP1-594E | U+249E8 | N/A | Identical to U+746F (KP0-D7D7) |
| KP1-59E2 | U+24ACA | U+2919C | |
| KP1-5A33 | U+24B3E | U+2C3A8 | |
| KP1-5AE3 | U+24C67 | U+2DED0 | |
| KP1-5B21 | U+7589 | U+24D01 | |
| KP1-5D4F | U+76CF | U+2506B | |
| KP1-5DCC | U+7714 | U+25133 | |
| KP1-6202 | U+2579B | U+2E0C4 | |
| KP1-622F | U+257D9 | U+257DF | |
| KP1-64DA | U+7C06 | U+25C83 | |
| KP1-68CB | U+7F80 | U+2E29A | Cognate but NUCV #402 |
| KP1-6E6A | U+8346 | N/A | Identical to U+834A (KP0-F3EC) |
| KP1-73E7 | U+8901 | U+2E590 | Cognate but no UCV |
| KP1-77D3 | U+8B82 | U+27B66 | |
| KP1-7818 | U+27BD5 | U+27BD6 | |
| KP1-792E | U+8CD2 | U+8CD6 | Reported by Andrew West via PRI #508 ReportIDID20250601101710 |
| KP1-8130 | U+4940 | U+28A6A | |
| KP1-83F7 | U+96DF | U+5DC2 | Reported by Judith Chen via PRI #497 ReportIDID20240328014549 |
| KP1-8699 | U+981A | U+2948D | |
| KP1-8AA9 | U+29A14 | U+5C33 | |
| KP1-8B6B | U+29B3B | U+2EAC4 | |
| KP1-8F3D | U+4CF9 | U+2A13A | |
| KP1-8FF5 | U+2A279 | U+400B | Reported by Michel Mariani via ReportIDID20250929183457 |
The table below provides details about known representative glyph issues that covers a total of six KP-source ideograph pairs or triplets, one pair or triplet per row and in increasing source reference order. A brief issue description is provide for each KP-source ideograph pair or triplet. While their current representative glyphs exhibit issues, it has been deemed prudent to leave them as-is without more information.
| Source References | Issue Description |
|---|---|
| KP0-E5A9, KP1-4ABB & KP1-4B0C | The representative glyphs of KP0-E5A9 (U+676E) and KP1-4B0C (U+67FF) are differentiated in the Unicode code charts, and the representative glyph of KP1-4ABB, which is unmapped, is identical to that of KP0-E5A9 (U+676E); this case is similar to that of KP0-F2A5 (U+6C9B), KP1-50BD (unmapped, and identical to KP0-F2A5 in that it uses the four-stroke 巿 component), and KP1-510B (unmapped, but different from KP0-F2A5 in that it uses the five-stroke 市 component) — see PRI #508 ReportIDID20250216091652 |
| KP0-E6C5, KP1-3861 & KP1-3862 | The representative glyphs of KP0-E6C5 (U+52FA) and KP1-3862 (U+FA77) are identical in the Unicode code charts, but without further information, it is prudent to leave them as-is; KP1-3861, whose representative glyph is different in that the stroke 丶 is replaced with 一, is unmapped; U+FA77 normalizes to U+52FA |
| KP0-E9B7, KP1-7699 & KP1-769A | The representative glyphs of KP0-E9B7 (U+8ABF) and KP1-769A (U+FAB9) are identical in the Unicode code charts, but without further information, it is prudent to leave them as-is; the representative glyph of KP1-7699 is identical to that of KP0-E9B7 and KP1-769A, and is unmapped; U+FAB9 normalizes to U+8ABF |
| KP0-FBFD, KP1-8833 & KP1-8834 | The representative glyphs of KP0-FBFD (U+98EE) and KP1-8833 (U+98F2) are identical in the Unicode code charts, but without further information, it is prudent to leave them as-is; the representative glyph of KP1-8834 is identical to that of KP0-FBFD and KP1-8833, and is unmapped |
| KP1-3A3A & KP1-5565 | The representative glyphs of KP1-3A3A (U+55A3) and KP1-5565 (U+24275) are identical in the Unicode code charts, but without further information, it is prudent to leave them as-is |
| KP1-62C7 & KP1-9285 | The representative glyphs of KP1-62C7 (U+418B) and KP1-9285 (U+9F9D) are differentiated in the Unicode code charts in the same way that their J-source representative glyphs are differentiated; their K-source representative glyphs are identical |
Another useful resource when researching DPRK character set standards is documentIRG N2839R5, which is the sixth version of a reconstructed version of the KPS 10721:2000 standard.
The following summarizes modifications from the previous version of this document:
© 2023–2026 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 UnicodeTerms 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.