Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://en.wikipedia.org/wiki/KS_X_1001 below:

KS X 1001 - Wikipedia

South Korean character set

"KS C 5601-1987" redirects here. For the encoded form assigned that label by Microsoft, see

.

KS X 1001, "Code for Information Interchange (Hangul and Hanja)",^[d][1] formerly called KS C 5601, is a South Korean coded character set standard to represent Hangul and Hanja characters on a computer.

KS X 1001 is encoded by the most common legacy (pre-Unicode) character encodings for Korean, including EUC-KR and Microsoft's Unified Hangul Code (UHC). It contains Korean Hangul syllables, CJK ideographs (Hanja), Greek, Cyrillic, Japanese (Hiragana and Katakana) and some other characters.

KS X 1001 is arranged as a 94×94 table, following the structure of 2-byte code words in ISO 2022 and EUC. Therefore, its code points are pairs of integers 1–94. However, some encodings (UHC and Johab), in addition to providing codes for every code point, provide additional codes for characters otherwise representable only as code point sequences.

This standard was previously known as KS C 5601. There have been several revisions of this standard. For example, there were revisions in 1987, 1992, 1998 and 2002.

The present, double-byte, Wansung (완성; Wanseong; lit. precomposing)^[1] character set was standardised by the third edition of KS C 5601,^[2] which was published in 1986.^[3] It is an ISO 2022 compatible encoding, typically used in EUC form, which assigns double-byte codes for non-Hangul, Hangul jamo, and the most common Hangul syllables, in contrast to Johab (조합; Johap; lit. combining)^[1] which is not compatible with ISO 2022, but assigns double-byte codes to all Hangul syllables using modern jamo.^[2] Wansung is technically a variable-length encoding, allowing other syllables to be represented with eight-byte sequences (using the jamo and Hangul Filler character), but this feature is not always implemented.^[4]

The earliest edition of KS C 5601, published in 1974,^[2] defined a variable-length^[2] 7-bit character set which assigned single-byte code points to 51^[3] basic Hangul jamo, somewhat analogously to JIS C 6220, in an encoding known as "N-byte Hangul".^[5] The second edition, published in 1982, retained the main character set from the 1974 edition but defined two supplementary sets, including a version of Johab. Neither edition was adopted as widely as intended.^[2]

Wansung was kept unchanged in the 1987 and 1992 editions. In the 1992 edition, additional annex material was added,^[3] including the definition of the Johab encoding^[6] in annex 3, and the older N-byte Hangul encoding in annex 4.^[1][5] It was published in response to industry use of Johab as a competing encoding to Wansung, being used at the time by Hangul Word Processor. Following the introduction of Unified Hangul Code by Microsoft in Windows 95, and Hangul Word Processor abandoning Johab in favour of Unicode in 2000, Johab ceased to be commonly used.^[2]

Encoding schemes of KS X 1001 include EUC-KR (in both ASCII and ISO 646-KR based variants, the latter of which includes a won currency sign (₩) at byte 0x5C rather than a backslash) and ISO-2022-KR,^[7] as well as ISO-2022-JP-2 (which also encodes JIS X 0208 and JIS X 0212). These all have the drawback that they only assign codes for the 2350 precomposed Hangul syllables which have their own KS X 1001 codepoints (out of 11172 in total, not counting those using obsolete jamo), and require others to use eight-byte composition sequences, which are not supported by some partial implementations of the standard.^[4]

The Johab encoding (stipulated in annex 3 of the 1992 version of the standard) and the EUC-KR superset known as Unified Hangul Code (UHC, also called Windows-949) provide single codes for all 11172 Hangul syllables.^[7][6] ISO-2022-KR and Johab are rarely used. Some operating systems extend this standard in other non-uniform ways, e.g. the EUC-KR extensions MacKorean on the classic Mac OS, and IBM-949 by IBM.

The Hangul Filler character is used to introduce eight-byte Hangul composition sequences^[8][9] and to stand in for an absent element (usually an empty final) in such a sequence.^[9]

Unicode includes the Wansung code Hangul Filler in the Hangul Compatibility Jamo block for round-trip compatibility, but uses its own system (with its own, differently used, filler characters) for composing Hangul. The KS X 1001 Hangul composition system is not used in Unicode, and the filler renders merely as an empty space; KS X 1001 composition sequences using modern jamo may be mapped to precomposed characters in Unicode.^[9] This is not usually done with Unified Hangul Code.

For round-trip compatibility, Unicode also includes the N-byte Hangul code Hangul Filler separately in the Halfwidth and Fullwidth Forms block, named the "Halfwidth Hangul Filler".

Following are the code charts for KS X 1001 in Wansung layout. Where a pair of hexadecimal numbers is given, the smaller is used when encoded over GL (0x21-0x7E), as in ISO-2022-KR when the Korean set has been shifted to, and the larger is used in the more typical case of it being encoded over GR (0xA1-0xFE), as in EUC-KR or UHC. Johab changes the arrangement to encode all 11172 Hangul clusters separately and in order.

To illustrate vendor differences in implementation, multiple Unicode mappings are shown for some characters. Apple's HangulTalk extensions to the Wansung plane (i.e. where both bytes are in the 0xA1-0xFE range) are shown, but other HangulTalk extension ranges are not. The additional codes for composed syllables in Unified Hangul Code, and IBM's extensions in IBM-949, are also not shown, since both fall outside of the Wansung plane.

The rows 41 and 94 may be used for user-defined purposes.^[10]

This set contains punctuation and other symbols, excluding punctuation present in KS X 1003 (which is included in row 3). Encodings which combine KS X 1001 with single-byte ASCII may use alternative Unicode mapping to the Halfwidth and Fullwidth Forms block for the backslash. Unicode mapping of the wave dash (tilde dash) also differs between vendors, and may be U+301C (favoured by IBM and Apple)^[11][12][13] or U+223C (favoured by Microsoft).^[14][15] Compare the similar but not identical handling of the JIS wave dash, and the handling of the tilde in the next row.

Except for the backslash, if two mappings are shown below, the first is used by Apple and the second is used by Microsoft.^[13][15]

This set contains additional punctuation and symbols. Similarly to the tilde character in the previous row, different mappings are used by Apple and Microsoft for the tilde character in this row (U+02DC by Apple, FF5E by Microsoft),^[13][15] which is intended to be shown as a raised tilde, whereas the tilde in the previous row is intended to be shown in-line at dash height.^[10] Mapping of the circled dot also differs.^[13][15]

The euro and registered trademark sign were added to the standard in 1998, while the Korean postal mark (㉾) was added in 2002.^[1] These three code points, as with the still-unused code points, have been put to use for other, non-standard, purposes by vendors, e.g. for boxed list markers by Apple.^[16] Microsoft updated its Unified Hangul Code implementation to add the 1998 additions including the euro sign, but did not add the Korean postal mark when it was added to the standard.^[17]

This set corresponds to KS X 1003 (the ISO 646 variant for Korean, a similar set to ASCII), but as two-byte codes preceded by 0x23 (or 0xA3 in GR-invoked (EUC) form). It includes the English alphabet / Basic Latin alphabet, western Arabic numerals and punctuation.

Compare the Roman set of JIS X 0201, which differs by including a Yen sign rather than a Won sign. Contrast the third rows of KPS 9566 and of JIS X 0208, which follow the ISO 646 layout but only include letters and digits.

Encodings such as EUC-KR and UHC combine KS X 1001 with single-byte ASCII or KS X 1003, and hence use alternative Unicode mappings to the Halfwidth and Fullwidth Forms block for the double-byte representations of these characters.

This set includes modern Hangul consonants, followed by vowels, both ordered by South Korean collation customs, followed by obsolete consonants. When used individually, these characters map to the Unicode Hangul Compatibility Jamo block, and do not have a one-to-one mapping with the position-specific characters in the Hangul Jamo block. Compare with row 4 of the North Korean KPS 9566. Character 04-52 is a Hangul Filler (see above), used in combining sequences.

This set contains Roman numerals and basic support for the Greek alphabet, without diacritics or the final sigma. Apple includes some additional punctuation in this row, as well as some black circled list markers continuing from those in row 6.^[16]

Contrast row 6 of KPS 9566, which includes the same characters but in a different layout.

This row contains characters for drawing boxes in a semigraphic context. Apple also includes some black circled list markers.^[16]

This row contains unit symbols as single characters, including those which consist of multiple letters. Apple also includes some circled list markers continuing from those in row 8.^[16]

Compare and contrast with the repertoire of unit symbols included in row 8 of KPS 9566.

This set contains Hiragana for writing the Japanese language. Apple also includes some bracketed list markers continuing from those in row 9.^[16]

Compare row 10 of KPS 9566, which uses the same layout. Compare and contrast row 4 of JIS X 0208, which also uses the same layout, but in a different row.

This set contains katakana for writing the Japanese language. However, the Japanese long vowel mark, which is used in katakana text and included in row 1 of JIS X 0208, is not included.^[20] Apple also includes some bracketed list markers continuing from those in rows 9 and 10.^[16]

Compare row 11 of KPS 9566, which uses the same layout. Compare and contrast row 5 of JIS X 0208, which also uses the same layout, but in a different row.

This set contains the modern Russian alphabet, and is not necessarily sufficient to represent other forms of the Cyrillic script. Apple also includes some black boxed list markers.^[16]

Compare row 5 of KPS 9566 and row 7 of JIS X 0208, which use the same layout (but in a different row).

Code points for precomposed Hangul are included in a continuous sorted block between code points 16-01 and 40-94 inclusive. Not all possible syllable clusters are included in this range. Compare the different ordering and availability in KPS 9566.

Initial+vowel+final syllables 뢨, 썅, 쏀, 쓩, and 쭁 are included but their initial+vowel counterparts 뢔, 쌰, 쎼, 쓔, and 쬬 are not. This can cause a problem with inputting, because input methods have to go through an initial+vowel syllable first in order to get to an initial+vowel+final syllable (e.g. ㅎ → 하 → 한).

Those which are not listed here may be represented using eight-byte composition sequences. All other modern-jamo clusters are assigned codes elsewhere by UHC. All possible modern-jamo clusters are assigned codes by Johab.

Initial consonants

Vowels

Final consonants

KS X 1001 encodes several Hanja with multiple readings multiple times. One character, 樂, is encoded four times. The first 268 characters (U+F900–U+FA0B) in the CJK Compatibility Ideographs block correspond to these duplicates.

In the table below, the first row-cell value (and reading) for each Hanja maps to the CJK Unified Ideographs block; others map to the CJK Compatibility Ideographs block.

• 한글: Hangul
• 한자: Hanja
• 특수문자: special characters (non-Hangul and non-Hanja characters)

KS X 1001, since 1992, also defines an alternative encoding known as Johab. This represents a Hangul syllable as the sequence of three five-bit values, split across two 8-bit bytes, most significant bit first. The most significant bit of the lead byte is always set (allowing combination with single-byte ASCII or KS X 1003). This encoding is also used for the modern jamo from row 4 of KS X 1001, by using the filler values for the other components. The Johab encoding for Hangul is shown in the table below.^[22]

Johab encodes the remainder of KS X 1001 using lead bytes which do not correspond to an initial jamo (0xE0–0xF9 for Hanja and 0xD9–0xDE^[23] for non-Hanja, excluding Hangul syllables and modern jamo), with trail bytes in the ranges 0x31–0x7E and 0x91–0xFE.^[22] These codes are algorithmically mapped from the characters' KS X 1001 code points,^[23] with two KS X 1001 rows per lead byte (compare and contrast Shift JIS).

The ASCII-based Johab encoding is numbered Code page 1361 by Microsoft.^[24] Other, vendor-defined, Johab variants also exist; for example, IBM defines one for use as a Shift Out set with EBCDIC. That variant uses shift in and shift out to switch between a single-byte EBCDIC page and Johab, uses a different encoding for the non-Hangul characters (using lead bytes 0x40–6C with a different layout), and uses lead bytes 0xD4–DD as a user-defined region, but uses the same Johab layout as the 1992 standard for the Hangul characters when in shift-out state.^[25] IBM number the EBCDIC-based, stateful Johab encoding Code page 1364,^[25] and also define a subset of that encoding, including fewer Hangul characters but in the same layout, as Code page 933.^[26]

Some other vendors such as Samsung or GoldStar (now LG) used other "Johab" encodings where the mappings of five-bit codes to jamo differ from the below, consequently not being compatible with the 1992 standard Johab.^[af] The table below corresponds to the 1992 standard and also to IBM usage.

This is the N-byte Hangul code,^[5] as specified by KS C 5601-1974 and by annex 4 of KS C 5601–1992. The second half of IBM's Code page 1040^[27] is a superset of this, assigning the characters ¢¬\~ (although not £) to the same locations as in Code page 1041, while the unextended N-Byte Hangul (besides C0 control code replacement graphics in some usage contexts, shared with IBM-1040) is Code page 891.^[28] Character 0x40/0xC0 is a Hangul Filler (see above), used in combining sequences.

Similarly to its Japanese counterpart JIS C 6220 (JIS X 0201), N-byte Hangul code could be used as a 7-bit encoding, with character allocations over the range 0x40 through 0x7C.^[5] The chart below shows the code in an 8-bit environment with the high bit set (i.e. over 0xC0 through 0xFC), as it is used in e.g. code page 891 or 1040.

1. ^ Missing Greek diacritics and final sigma.
2. ^ Missing chōonpu, shinjitai, kokuji.
3. ^ ^{a b} Missing lowercase å, although the uppercase U+212B Å ANGSTROM SIGN is included, as are both cases of Ø and Æ.
4. ^ Korean: 정보 교환용 부호계 (한글 및 한자); RR: Jeongbo Gyohwannyong Buhogye (Hangeul mit Hanja)
5. ^ ^{a b} As a ISO 2022 compatible 94ⁿ-character set, the plain space and delete character are always available as single-byte codes at 0x20 and 0x7F (not 0xA0 and 0xFF) respectively.
6. ^ ^{a b c d e f g h i} Mapped by Apple to a sequence of the ASCII digit, the combining square U+20DE, and the private-use character U+F87C.^[16] Appearance shown here simulated.
7. ^ ^{a b c d e f g h i j k} Mapped by Apple to an ASCII sequence with the number in square brackets, prefixed by the private-use character U+F863.^[16] Appearance shown here simulated.
8. ^ Narrower than 0xA2D2. Apple appends a private-use character U+F87F for round trip purposes.
9. ^ Two vertical lines with right-hand line bolder. Apple maps this to the ordinary double vertical U+2016 (‖) plus a private-use character U+F87B for round trip purposes; U+1D102 is shown here to reflect the intended appearance.
10. ^ Two vertical lines with left-hand line bolder. Apple maps this to the ordinary double vertical U+2016 (‖) plus a private-use character U+F87C for round trip purposes; U+1D103 is shown here to reflect the intended appearance.
11. ^ Variant aligned to the bottom-left of the character cell, for horizontal use. Apple maps this to U+FF01+F874, where U+F874 is a private-use character used by Apple to tag the character for round-tripping purposes.^[16] More recently,^[18] a standardised variation sequence has been added for this form, using an appended Variation Selector 1 (U+FE00).^[19]
12. ^ Variant aligned to the bottom-left of the character cell, for horizontal use. Apple maps this to U+3002+F87D, where U+F87D is a private-use character used by Apple to tag the character for round-tripping purposes.^[16] More recently,^[18] a standardised variation sequence has been added for this form, using an appended Variation Selector 1 (U+FE00).^[19]
13. ^ ^{a b} Duplicate, mapped by Apple with an appended private-use character U+F87F for round tripping.^[16]
14. ^ An exact match does note exist in Unicode, shown simulated. Apple maps to U+3257+F87A, where U+F87A is a private-use character, and U+3257 is the unfilled circled character.^[16]
15. ^ An exact match does note exist in Unicode, shown simulated. Apple maps to U+3258+F87A, where U+F87A is a private-use character, and U+3258 is the unfilled circled character.^[16]
16. ^ An exact match does note exist in Unicode, shown simulated. Apple maps to U+3259+F87A, where U+F87A is a private-use character, and U+3259 is the unfilled circled character.^[16]
17. ^ An exact match does note exist in Unicode, shown simulated. Apple maps to U+325A+F87A, where U+F87A is a private-use character, and U+325A is the unfilled circled character.^[16]
18. ^ An exact match does note exist in Unicode, shown simulated. Apple maps to U+3251+F87A, where U+F87A is a private-use character, and U+3251 is the unfilled circled character.^[16]
19. ^ An exact match does note exist in Unicode, shown simulated. Apple maps to U+3252+F87A, where U+F87A is a private-use character, and U+3252 is the unfilled circled character.^[16]
20. ^ An exact match does note exist in Unicode, shown simulated. Apple maps to U+3253+F87A, where U+F87A is a private-use character, and U+3253 is the unfilled circled character.^[16]
21. ^ An exact match does note exist in Unicode, shown simulated. Apple maps to U+3254+F87A, where U+F87A is a private-use character, and U+3254 is the unfilled circled character.^[16]
22. ^ An exact match does note exist in Unicode, shown simulated. Apple maps to U+3255+F87A, where U+F87A is a private-use character, and U+3255 is the unfilled circled character.^[16]
23. ^ An exact match does note exist in Unicode, shown simulated. Apple maps to U+3256+F87A, where U+F87A is a private-use character, and U+3256 is the unfilled circled character.^[16]
24. ^ ^{a b c d e f g h i j} Mapped by Apple to an ASCII sequence, prefixed by the private-use character U+F862.^[16]
25. ^ ^{a b c d e f g h i} Mapped by Apple to a sequence of the ASCII digit, the combining square U+20DE, and the private-use character U+F875.^[16] Appearance shown here simulated.
26. ^ ^{a b c d e f g h i j k} Mapped by Apple to an ASCII sequence with the number in square brackets, prefixed by the private-use character U+F866.^[16] Appearance shown here simulated.
27. ^ ^{a b c d} These largely duplicate characters in row 1. Apple describes them as "long" versions, and appends the private-use character U+F879 for round-tripping purposes.^[16]
28. ^ ^{a b c d} The MacKorean encoding also includes several sets of differently styled arrows (including white arrows) outside of the KS X 1001 plane ranges, with lead bytes 0xA8 and 0xAC, and trail bytes between 0x41 and 0xA0. Apple appends the private-use character U+F878 to this particular set of white arrows for round-tripping purposes.^[16]
29. ^ ^{a b} Unlike those in row 1, these two marks are intended to display in low position (similarly to U+301F). Apple appends the private-use character U+F873 to distinguish them.^[16]
30. ^ Apple maps this to U+21E7+F87F, where U+21E7 is the white up arrow^[16] and U+F87F is a private-use character, although this character is a black arrow.^[21] The character shown is a Unicode character which postdates Apple's mapping table, and resembles the glyph^[21] for this MacKorean character.
31. ^ Apple maps this to a sequence of the ASCII exclamation mark followed by the private-use character U+F87F.^[16]
32. ^ Some mappings for these encodings are available here.
33. ^ ^{a b c d} Were this one used, it would result in a trail byte in the C0 control codes range.
34. ^ ^{a b c d} Were this one used, it would result in trail bytes in the 0x2_ and 0x3_ rows of ASCII. Johab does not use the 0x2_ row for trail bytes, similarly to most common legacy CJK encodings (compare Shift JIS, GBK, Big5). The EBCDIC-based version of Johab does not use trail bytes from either row, due to them being in the EBCDIC control code range.

1. ^ ^{a b c d e} Lunde, Ken (2009). "Chapter 3: Character Set Standards". CJKV Information Processing. "O'Reilly Media, Inc.". pp. 143–148. ISBN 978-0596514471.
2. ^ ^{a b c d e f} Hwang, Jinsang (2005). The Social Shaping of ICTs Standards: A Case of National Coded Character Set Standards Controversy in Korea (PDF). University of Edinburgh.
3. ^ ^{a b c} Lunde, Ken (1995-12-18). "2.4.6: Obsolete Standards". CJK.INF Version 1.9.
4. ^ ^{a b} Shin, Jungshik. "What are KS X 1001(KS C 5601) and other Hangul codes?". Hangul & Internet in Korea FAQ.
5. ^ ^{a b c d} Lunde, Ken (1995-12-18). "3.3.6: N-byte Hangul". CJK.INF Version 1.9.
6. ^ ^{a b} "INFO: Hangul (Korean) Character Sets", Microsoft Support, Microsoft
7. ^ ^{a b} Zsigri, Gyula (2002-06-18). "KSC and UHC".
8. ^ Chang, Hye-Shik (28 November 2021). "cpython/Modules/cjkcodecs/_codecs_kr.c (revision d3faf43)". cPython source tree. Python Software Foundation.
9. ^ ^{a b c} Chung, Jaemin (2017-03-30). Proposal to add an informative note to U+3164 HANGUL FILLER (PDF). Unicode Consortium. UTC L2/17-081.
10. ^ ^{a b} Korea Bureau of Standards (1988-10-01). Korean Graphic Character Set for Information Interchange (PDF). ITSCJ/IPSJ. ISO-IR-149.
11. ^ "ibm-1363_P110-1997 (lead byte A1)". ICU Demonstration - Converter Explorer. International Components for Unicode / Unicode Consortium.
12. ^ "euc-kr (lead byte A1)". ICU Demonstration - Converter Explorer. International Components for Unicode.
13. ^ ^{a b c d} "Map (external version) from Mac OS Korean encoding to Unicode 3.2 and later". Apple.
14. ^ "windows-949-2000 (lead byte A1)". ICU Demonstration - Converter Explorer. International Components for Unicode / Unicode Consortium.
15. ^ ^{a b c d} "Lead Byte A1-A2 (Code page 949)". MSDN. Microsoft. 6 February 2008.
16. ^ ^{a b c d e f g h i j k l m n o p q r s t u v w x y z aa ab ac ad ae} Apple (2005-04-05). "Map (external version) from Mac OS Korean encoding to Unicode 3.2 and later". Unicode Consortium.
17. ^ "windows-949-2000 (lead byte A2)". ICU Demonstration - Converter Explorer. International Components for Unicode / Unicode Consortium.
18. ^ ^{a b} Lunde, Ken (2018-01-21). "Proposal to add standardized variation sequences for fullwidth East Asian punctuation" (PDF). UTC L2/17-436.
19. ^ ^{a b} "StandardizedVariants.txt: Standardized Variation Sequences". Unicode Character Database. Unicode Consortium.
20. ^ Lunde, Ken (2009). "Seemingly Missing Characters". CJKV Information Processing: Chinese, Japanese, Korean & Vietnamese Computing (2nd ed.). Sebastopol, CA: O'Reilly. p. 180. ISBN 978-0-596-51447-1.
21. ^ ^{a b} Lunde, Ken (2009). "Appendix E: Vendor Character Set Standards" (PDF). CJKV Information Processing: Chinese, Japanese, Korean & Vietnamese Computing (2nd ed.). Sebastopol, CA: O'Reilly. ISBN 978-0-596-51447-1.
22. ^ ^{a b c} Lunde, Ken (2008). "Chapter 4: Encoding Methods (§ Johab Encoding—KS X 1001:2004)". CJKV Information Processing (2nd ed.). Sebastopol, California: O'Reilly Media. pp. 268–273. ISBN 978-0-596-51447-1.
23. ^ ^{a b} Shin, Jungshik (2011-10-14) [1999-08-16]. Johab to Unicode table. Unicode Consortium.
24. ^ "Code Page Identifiers". Windows Dev Center. Microsoft. 7 January 2021.
25. ^ ^{a b} "ibm-1364_P110-2007". International Components for Unicode. Unicode Consortium.
26. ^ "ibm-933_P110-1995". International Components for Unicode. Unicode Consortium.
27. ^ "Code Page 01040" (PDF). IBM. Archived (PDF) from the original on 2015-07-08.
28. ^ "Code Page 00891" (PDF). IBM. Archived (PDF) from the original on 2015-07-08.
29. ^ "KSRI-87-37-IR: 한글·한자 코드 표준화에 관한 연구: A Study on Standardization of Hangul and Hanja Codes" (PDF) (in Korean). Ministry of Science and Technology. 1987. p. 68. Archived from the original (PDF) on 2019-03-01.