File:Unified Hangul Code.svg
Original file (SVG file, nominally 1,031 × 990 pixels, file size: 28 KB)
Captions
DescriptionUnified Hangul Code.svg |
English: Basic structure of the Unified Hangul Code (UHC), also called Windows-949 or IBM-1363.
The single byte region does not accept a second byte, hence it is shown occupying the entire width of the encoding space diagram. It is either treated as ISO-646-KR (defined by KS C 5636, later renamed KS X 1003), e.g. in localised fonts or IBM's Unicode mapping, or treated as US-ASCII, e.g. in Unicode mapping on Windows. Standard Wansung codes (as originally defined by KS C 5601:1987, now called KS X 1001:1987) are represented the same as in EUC-KR, i.e. as their ISO 2022 codes designated to GR. Wansung (unlike e.g. the Johab code defined by KS C 5601:1992 annex 3) only encodes the most common Hangul syllables precomposed, not all that could conceivably be required (although it does allow the others to be represented by four-character combining sequences in which the first character is a Hangul Filler). The extended Hangul region encodes all other possible modern-Jamo Hangul syllables in Unicode order, but with those already present in Wansung code skipped. Gaps in the extended Hangul region are due to UHC not using non-alphabetical ASCII bytes as trail bytes. 0x80 and Eight Ones (0xFF) are never used as a lead or trail byte (although they might get best-fit mapped to U+0080 and private use U+F8F7 respectively). See also:
Wansung, Johab and UHC are South Korean encodings. With respect to North Korea, the encoded form of KPS 9566:2003 documented by the Unicode Consortium appears to use a similar and most probably strongly inspired structure, but with a updated revision of KPS 9566:1997 (the DPRK equivalent of Wansung code) in the EUC region, and with a different sequence in the extended Hangul region (due to the Hangul repertoire of KPS 9566:1997 not being the same as that of Wansung, and due to North Korea using a different ordering of the jamo). Contrast with File:IBM Korea KS PC-Data encoding (IBM-949).svg, which is the IBM-949 encoding, serving to illustrate the different meanings of "code page 949" between Microsoft and IBM (the extensions are mutually incompatible and the common subset is basically just EUC-KR; Windows-949 corresponds to IBM-1363). Also worth comparing and contrasting with File:GBK encoding.svg, another encoding which extends the double byte repertoire of an EUC base encoding, but which takes a different approach in some ways.한국어: 통합형 한글 코드(w:ko:코드 페이지 949) |
||||||
Date | |||||||
Source | Own work | ||||||
Author | User:HarJIT | ||||||
Permission (Reusing this file) |
I, the copyright holder of this work, hereby publish it under the following licenses:
This file is licensed under the Creative Commons Attribution 4.0 International license. Attribution: HarJIT
You may select the license of your choice. |
||||||
Other versions | File:Cp949-map.png Smaller version, raster, older, Korean language text. Not used as a source for this: I only became aware of it subsequent to creating this one. |
File history
Click on a date/time to view the file as it appeared at that time.
Date/Time | Thumbnail | Dimensions | User | Comment | |
---|---|---|---|---|---|
current | 09:48, 13 December 2021 | 1,031 × 990 (28 KB) | HarJIT (talk | contribs) | Yet another font change since Commons no longer has that one either. | |
12:27, 4 January 2020 | 1,031 × 990 (26 KB) | HarJIT (talk | contribs) | Likewise with the trail bytes. | ||
19:17, 2 January 2020 | 1,031 × 990 (26 KB) | HarJIT (talk | contribs) | 0x80 isn't actually used as a lead byte (somehow this had escaped my notice). | ||
08:27, 5 April 2018 | 1,031 × 990 (33 KB) | HarJIT (talk | contribs) | Hopefully makes it less ugly. | ||
08:22, 5 April 2018 | 1,031 × 990 (32 KB) | HarJIT (talk | contribs) | Remove unmatched label. | ||
08:20, 5 April 2018 | 1,031 × 990 (34 KB) | HarJIT (talk | contribs) | Retypeset with Ubuntu font family rather than Roboto, is available on WMF server. | ||
20:39, 2 January 2018 | 1,030 × 989 (239 KB) | HarJIT (talk | contribs) | Evidently I overlooked that. | ||
20:00, 2 January 2018 | 1,030 × 989 (231 KB) | HarJIT (talk | contribs) | Give ranges. | ||
14:31, 2 January 2018 | 1,030 × 989 (147 KB) | HarJIT (talk | contribs) | Mention what the single byte codes are, and give other names for standards. | ||
21:37, 1 January 2018 | 1,030 × 989 (119 KB) | HarJIT (talk | contribs) | Use sane nominal pixel dimensions. |
You cannot overwrite this file.
File usage on Commons
There are no pages that use this file.
File usage on other wikis
The following other wikis use this file:
- Usage on en.wikipedia.org
- Usage on www.wikidata.org
Metadata
This file contains additional information such as Exif metadata which may have been added by the digital camera, scanner, or software program used to create or digitize it. If the file has been modified from its original state, some details such as the timestamp may not fully reflect those of the original file. The timestamp is only as accurate as the clock in the camera, and it may be completely wrong.
Width | 1030.892 |
---|---|
Height | 989.8595 |