Menu
Home Explore People Places Arts History Plants & Animals Science Life & Culture Technology
On this page
Code page 949 (IBM)
IBM/AIX character encoding for Korean

IBM code page 949 (IBM-949) is a character encoding which has been used by IBM to represent Korean language text on computers. It is a variable-width encoding which represents the characters from the Wansung code defined by the South Korean standard KS X 1001 in a format compatible with EUC-KR, but adds IBM extensions for additional hanja, additional precomposed Hangul syllables, and user-defined characters.

Giving values in hexadecimal, bytes 0x00 through 0x7F are used for single byte KS X 1003 (ISO 646:KR) characters, a similar set to ASCII but with a won sign rather than a backslash. Bytes 0x80 through 0x84 are used for IBM single byte extension characters. Lead bytes 0x8F through 0xA0 are used for IBM double byte extension characters. Lead bytes 0xA1 through 0xFE are used for Wansung code (KS X 1001 characters in EUC-KR form, double byte), but with some unused space opened up for user-defined use.

Although both are sometimes named "cp949", IBM-949 is different from Windows code page 949 (IBM-1363), which is Microsoft's Unified Hangul Code, a different extension of EUC-KR. It should also not be confused with IBM's implementation of plain EUC-KR (IBM-970). Code page 949 in OS/2 is the IBM code page; however, a third-party patch exists to change this.

Related Image Collections Add Image
Profiles
1 Image
We don't have any YouTube videos related to Code page 949 (IBM) yet.
We don't have any PDF documents related to Code page 949 (IBM) yet.
We don't have any Books related to Code page 949 (IBM) yet.
We don't have any archived web articles related to Code page 949 (IBM) yet.

Terminology and encoding labelling

Both IBM-949 and Unified Hangul Code (Windows-949) are known as "code page 949" (or "cp949") although they share only the EUC-KR subset in common. Neither has a standardised IANA-registered label to identify it. Although UHC is included in the WHATWG Encoding Standard,2 with labels including "windows-949",3 IBM-949 is not. IBM-949 therefore is not permitted in HTML5.

Although the meaning of the label "ibm-949" (and conversely "windows-949" and "ms949") is unambiguous where these labels are supported, the interpretation of the encoding labels "949" and "cp949" consequently varies between implementations. For example, International Components for Unicode uses "cp949", "949", "ibm-949" and "x-IBM949" to refer to IBM-949,4 and additionally the labels "cp949c", "ibm-949c" and "x-IBM949C" to refer to an variant which uses unmodified ASCII mappings for 0x20–7E (resulting in duplicate mappings for the backslash),5 while (of the labels incorporating the code page number 949) only "ms949" and "windows-949" are assigned to UHC.6 This is in contrast to Python, which recognises both "cp949" and "949" (in addition to the more explicit "ms949" and "uhc", but not "windows-949") as labels for UHC, and does not include an IBM-949 codec.7 The code page 949 used by Korean language versions of OS/2 is the IBM code page; to add support for the entire Unicode set of Korean syllables, a third-party patch exists to replace it with the Microsoft code page.8

IBM-949 is a variable width encoding defined as the combination of two fixed-width code pages, the single-byte Code page 1088 and the double-byte Code page 951.91011

History

A version of Code page 951 (a DBCS-PC, i.e. double-byte non-EUC non-EBCDIC, code), the double-byte component for IBM-949, is defined in the September 1992 revision of IBM Corporate Specification C-H 3-3220-125, along with Code page 834 (a DBCS-Host, i.e. double-byte EBCDIC, code), which is the double byte component of Code page 933.12 This version of Code page 949/951 considered the entire lead byte range 0x8F–A0 to be a user-defined region, and included only standard Wansung assignments and user-defined areas, thus not including some characters which Code page 933/834 included.13 Some later versions, such as that implemented by International Components for Unicode (ICU), shrink the user-defined region to include these characters as extensions.14

The earlier October 1989 revision of C-H 3-3220-125 had instead defined Code page 926 as its DBCS-PC code, which encoded the same characters as IBM-834 in a layout differing from both IBM-951 and IBM-834, which had a different lead byte range and was not an EUC-KR extension.15 IBM-926 was combined with Code page 891 or Code page 1040 (respectively 8-bit N-byte Hangul Code and an extension thereof; compare how Shift JIS extends 8-bit JIS X 0201) to form IBM-934 or IBM-944 respectively.1617

Code page 944/926 are now deprecated in favour of IBM-949. The 1992 revision designates code page 926 as "restricted" ("limited to the particular environment for which [it is] registered") and does not give its chart or mappings from the other code pages,18 and CCSID 944 is categorised as "coexistence and migration"19 (contrast "interoperable" for CCSID 949).20 International Components for Unicode includes Unicode mappings for IBM-9492122 and IBM-933, but its IBM-944 mapping was removed in 2001.23

Single byte codes

IBM code page 949 (single byte component: 1088)2425262728
0123456789ABCDEF
0xNUL┌┐└┘│─•◘○◙♂♀♪♫☼
1x┼◄↕‼┴┬┤↑├→←∟↔▲▼
2x SP !"#$%&'()*+,-./
3x0123456789:;<=>?
4x@ABCDEFGHIJKLMNO
5xPQRSTUVWXYZ[₩]^_
6x`abcdefghijklmno
7xpqrstuvwxyz{|}~⌂
8x¢¬\‾¦8F
9x909192939495969798999A9B9C9D9E9F
AxA01-_2-_3-_4-_5-_6-_7-_8-_9-_10-_11-_12-_13-_14-_15-_
Bx16-_17-_18-_19-_20-_21-_22-_23-_24-_25-_26-_27-_28-_29-_30-_31-_
Cx32-_33-_34-_35-_36-_37-_38-_39-_40-_41-_42-_43-_44-_45-_46-_47-_
Dx48-_49-_50-_51-_52-_53-_54-_55-_56-_57-_58-_59-_60-_61-_62-_63-_
Ex64-_65-_66-_67-_68-_69-_70-_71-_72-_73-_74-_75-_76-_77-_78-_79-_
Fx80-_81-_82-_83-_84-_85-_86-_87-_88-_89-_90-_91-_92-_93-_94-_
  Differences from code page 437 (for 0x00–7F) or EUC-KR (for 0x80–FF)

Double byte codes

Lead bytes 0x8F–99, 0xC9, 0xFE (user-defined ranges)

IBM-949 is designed to support a maximum of 1880 UDC (user-defined characters),29 including the user-defined rows (lead bytes 0xC9 and 0xFE) of the Wansung plane, and ranges outside the Wansung plane. In this version, the lead bytes 0x8F–A0 contain a maximum of 1692 UDC, and lead bytes 0xC9 and 0xFE contain a maximum of 94 each (i.e. with trail bytes 0xA1–FE).30 However, when the extensions to support the entire double-byte repertoire of IBM-933 are implemented, they use lead bytes 0x9A–A0, resulting in a smaller maximum number of characters left for user definition.3132

When mapped to Unicode, 0xC9A1–C9FE (between the syllable and hanja ranges) are mapped to the Unicode Private Use Area code points U+E000–E05D, while 0xFEA1–FEFE (between the end of the hanja range and the end of the plane) are mapped to U+E05E–E0BB. Outside the Wansung plane, 0x8FA0–9AA5 (where the second byte is in the range 0xA1–FE) are mapped to the Private Use Area code points U+E0BC–E4CA.33 The last of these ranges cuts into the start of the 0x9A row (shown below).

Collectively these private use ranges cover the code points U+E000–E4CA, allowing 1227 UDC to be mapped from IBM-949 to Unicode.34 The separate private use area range U+F843–F86E is used by IBM to map some characters within the extended hanja range.35 This follows early recommendations from the Unicode Consortium that corporate characters be allocated from U+F8FF downward and user-defined characters be allocated from U+E000 upward,36 and is part of a larger corporate private use area scheme which is defined internally by IBM, and uses the range U+F83D–F8FF.3738

Lead bytes 0x9A–9D (extended symbols and hanja)

According to the 1992 specification, this entire range is user-defined.39 As implemented in the codec contributed to ICU by IBM, however, 0x9AA1 through 0x9AA5 are the end of the user-defined range. The remainder of this range includes some non-Hangul characters included in Code page 933 but not in Wansung code. 0x9AA6 through 0x9AAB contain miscellaneous technical or mathematical symbols. The remainder contains hanja additional to those included in KS X 1001, although some are mapped by IBM to the Private Use Area.40

IBM code page 949 (extended symbols and hanja)4142
0123456789ABCDEF
9AAxǂ43≦≧K￤ʺ喀擱羯酣
9ABx醵骼蒹哽扃檠熲畊稧雞杲瞽詁栱槓箜
9ACx蝌霍盥鸛鉸佝傴媾嫗晷甌覯颶掬跪巹
9ADx漌岌笈覇鰭唜糯喃曩迺佞獰孥鬧靼怛
9AEx闥韃党蟷碓菟咄垌肚蚪滕灯鐙犖幱埓
9AFx榔涼魎癘膂蠡鑢櫟鬣昤泠苓蛉潦艫
9BAx轤漉祿轆籟蕾誄寥僂髏窿凛廩提漓
9BBx离螭魑痳岦媽蟇謾鏝鬘魍眛苺脉俛耄
9BCx鉾濛矇瀰糜閩婆欂牔胖髣魴潘翻辟汴
9BDx辮遍駢彆迸鴇黼蝠丰葑仆罘苻蜉頫鮒
9BEx吟蕡巿髴黻妣沙沘睥篦腓轡髀擯蘋贇
9BFx顰鬢姒麝楂槎笥槊鑠歃鍤霎殤鰓噬
9CAx婿齟射單尠愃洗燹霰偰契挈艘霄蟀
9CBx瑣叟宿晬溲祟雎鶉虱啻寺緦矧瑟萼贋
9CCx鴈戞遏嵒諳黯鞅欸皚礙靉阨射篛籥羘
9CDx敔恚射羨臙蠕讌塩饜嬰睨翳蕋遨媼薀
9CEx鰮蕘舂蛹吁熨蜿幃衞囿帷蕤黝鬻檼珢
9CFx齦挹栮頣仞眥粢耔觜赭柞潜蚕嶂瘴
9DAx装纔柢蛆豬糴囀巓磚翦窃椄梃晢瑅
9DBx踶吊噪皁竈笊糶絛鯛樅蹤蔟肘隼則証
9DCx痣湌慚刱44悵氅簀蜴躑濺簷蜻砌靆峭綃
9DDx鈔鞘數躅髑怱葱摧槌甃箒鞦麁麤杻舳
9DEx冲橇贅巵徴鵄忱拆橐駄幀蝙庖炮舖鉋
9DFx鞄分蓖蹕瘧邯鷳炕廨慊篋陜皞醐鶻

Lead bytes 0x9E–A0 (extended hanja and hangul syllables)

According to the 1992 specification, this entire range is user-defined.45 As implemented in the codec contributed to ICU by IBM, 0x9EA1 through 0x9EAC contain the remainder of the extended hanja. The rest of the range contains a few additional Hangul syllables which are not available in pre-composed form in pure EUC-KR. Unlike Unified Hangul Code, this is insufficient to support all non-partial Johab syllables absent in Wansung code.46

Significant amongst these are 뢔 (0x9EFC), 쌰 (0x9FE6), 쎼 (0x9FED), 쓔 (0x9FF3) and 쬬 (0xA0C1), which correspond to the beginnings of the standard Wansung characters 뢨, 썅, 쏀, 쓩, and 쭁 respectively, when partly entered in an input method editor.

IBM code page 949 (extended hanja and hangul syllables)47
0123456789ABCDEF
9EAx鑊圜懽鬟媓怳囂猴篌忻迄頡갂갋걹
9EBx겇겓곩곺괙괨괫궛귕귬긂긏긑긧긼깄
9ECx깉깢꺠꼄꼳꽌꽘꽛꽨꾓꾲꾿꿘꿧뀍뀡
9EDx끠낐낻냬넏넞녇녓녙녯녺놧놰눳늧닁
9EEx닑닠댱댸덨덪뎜돓됀됏됬둗둿뒴듁듧
9EFx딮딲딷딿땨떄뗴뚀뚸뜌럐렏뢔룜뤗
9FAx릐맟맻먜멫멭몀몯뫃뫠믁믕믜믠밎
9FBx밨밷뱜뱨벘벜벹볌볒볓볔봣붗붴븘븡
9FCx븨빋뺜뺴뻭뻰뻴뻿뼤뽜뽸뿀뿕뿝뿨쀄
9FDx쀠쁙쁴삮삷삻샃샇샏섥섿셑셗솓솻슌
9FEx슳싀싦쌂쌋쌧쌰썃썌썻쎅쎙쎠쎼쏼쐿
9FFx쑷쒓쓓쓔씼씿앏앟얐얫얶엱엳옝옫
A0Ax옺욷웟윋윶읻잧잪젇젔젛젹졋좐좜
A0Bx좠좬좰좸죨죰죱줫쥭즤짔쨰쩗쩰쪗쪠
A0Cx쫒쬬쮀쯥쯰찟찦찯찿챂챱챼쳣쳥쵀췃
A0Dx츼칻캗캩컈컽켙쾍쾐쾟쾬쾽킈턔텠텩
A0Ex퉷튓틍틧팊팦퍙퍠펲펵폇퐤풰퓩픅픐
A0Fx픙픠픤핟핡핬핱햬헏혬횩횸훕휌흭

Lead bytes 0xA1–C8, 0xCA–FD (standard Wansung)

Further information: KS X 1001 § Wansung code charts

See also

Footnotes

References

  1. Borgendale, Ken. "OS/2 Codepage and Keyboard Display Tools". http://www.borgendale.com/tools/tools.htm ↩

  2. van Kesteren, Anne, "5. Indexes (§ index EUC-KR)", Encoding Standard, WHATWG, This matches the KS X 1001 standard and the Unified Hangul Code, more commonly known together as Windows Codepage 949. /wiki/Anne_van_Kesteren ↩

  3. van Kesteren, Anne. "4.2. Names and labels". Encoding Standard. WHATWG. /wiki/Anne_van_Kesteren ↩

  4. "Converter Explorer: ibm-949_P110-1999 (alias x-IBM949)", International Components for Unicode, Unicode Consortium http://icu4c-demos.unicode.org/icu-bin/convexp?conv=ibm-949_P110-1999&s=ALL ↩

  5. "Converter Explorer: ibm-949_P11A-1999 (alias x-IBM949C)", International Components for Unicode, Unicode Consortium. This is the ASCII-based version of IBM-949. http://icu4c-demos.unicode.org/icu-bin/convexp?conv=ibm-949_P11A-1999&s=ALL ↩

  6. "windows-949-2000", Converter Explorer, International Components for Unicode http://demo.icu-project.org/icu-bin/convexp?conv=windows-949-2000 ↩

  7. "codecs — Codec registry and base classes § Standard Encodings". Python 3.7.2 documentation. Python Software Foundation. https://docs.python.org/3.7/library/codecs.html#standard-encodings ↩

  8. Borgendale, Ken. "OS/2 Codepage and Keyboard Display Tools". http://www.borgendale.com/tools/tools.htm ↩

  9. "Coded character set identifiers: CCSID 949". IBM Globalization. IBM. Archived from the original on 2014-11-29. https://web.archive.org/web/20141129233846/http://www-01.ibm.com/software/globalization/ccsid/ccsid949.html ↩

  10. "CCSID 1088 information document". Archived from the original on 2016-03-26. https://web.archive.org/web/20160326215133/http://www-01.ibm.com/software/globalization/ccsid/ccsid1088.html ↩

  11. "Code page 951 information document". Archived from the original on 2017-01-16. https://web.archive.org/web/20170116144609/https://www-01.ibm.com/software/globalization/cp/cp00951.html ↩

  12. "IBM Korean Graphic Character Set: DBCS-Host and DBCS-PC" (PDF). IBM. 2001 [1992]. C-H 3-3220-125 1992-09. https://public.dhe.ibm.com/as400/products/clientaccess/win32/files/globalization/Korean_base1992.pdf ↩

  13. "IBM Korean Graphic Character Set: DBCS-Host and DBCS-PC" (PDF). IBM. 2001 [1992]. C-H 3-3220-125 1992-09. https://public.dhe.ibm.com/as400/products/clientaccess/win32/files/globalization/Korean_base1992.pdf ↩

  14. International Components for Unicode (ICU), ibm-949_P110-1999.ucm, 2002-12-03 https://github.com/unicode-org/icu/blob/master/icu4c/source/data/mappings/ibm-949_P110-1999.ucm ↩

  15. "IBM Korean Graphic Character Set: DBCS-Host and DBCS-PC" (PDF). IBM. 2001 [1992]. C-H 3-3220-125 1992-09. https://public.dhe.ibm.com/as400/products/clientaccess/win32/files/globalization/Korean_base1992.pdf ↩

  16. "Coded character set identifiers: CCSID 934". IBM Globalization. IBM. Archived from the original on 2014-12-02. https://web.archive.org/web/20141202014525/http://www-01.ibm.com/software/globalization/ccsid/ccsid934.html ↩

  17. "Coded character set identifiers: CCSID 944". IBM Globalization. IBM. Archived from the original on 2014-12-01. https://web.archive.org/web/20141201233858/http://www-01.ibm.com/software/globalization/ccsid/ccsid944.html ↩

  18. "IBM Korean Graphic Character Set: DBCS-Host and DBCS-PC" (PDF). IBM. 2001 [1992]. C-H 3-3220-125 1992-09. https://public.dhe.ibm.com/as400/products/clientaccess/win32/files/globalization/Korean_base1992.pdf ↩

  19. "Coded character set identifiers: CCSID 944". IBM Globalization. IBM. Archived from the original on 2014-12-01. https://web.archive.org/web/20141201233858/http://www-01.ibm.com/software/globalization/ccsid/ccsid944.html ↩

  20. "Coded character set identifiers: CCSID 949". IBM Globalization. IBM. Archived from the original on 2014-11-29. https://web.archive.org/web/20141129233846/http://www-01.ibm.com/software/globalization/ccsid/ccsid949.html ↩

  21. "Converter Explorer: ibm-949_P110-1999 (alias x-IBM949)", International Components for Unicode, Unicode Consortium http://icu4c-demos.unicode.org/icu-bin/convexp?conv=ibm-949_P110-1999&s=ALL ↩

  22. International Components for Unicode (ICU), ibm-949_P110-1999.ucm, 2002-12-03 https://github.com/unicode-org/icu/blob/master/icu4c/source/data/mappings/ibm-949_P110-1999.ucm ↩

  23. Viswanadha, Ram (2001-11-01). "ICU-1281 Remove unwanted ucmfiles". International Components for Unicode. https://github.com/unicode-org/icu/commit/4b5d175d834a24a0ec08fbbf1d2e20385ef78af1#diff-8403419f92b19da4ade420a7d6a94b603a7d0bd5f62d672eee888a62f50a2886 ↩

  24. Code Page CPGID 01088 (pdf) (PDF), IBM https://public.dhe.ibm.com/software/globalization/gcoc/attachments/CP01088.pdf ↩

  25. Code Page CPGID 01088 (txt), IBM https://public.dhe.ibm.com/software/globalization/gcoc/attachments/CP01088.txt ↩

  26. "Converter Explorer: ibm-949_P110-1999 (alias x-IBM949)", International Components for Unicode, Unicode Consortium http://icu4c-demos.unicode.org/icu-bin/convexp?conv=ibm-949_P110-1999&s=ALL ↩

  27. "Converter Explorer: ibm-949_P11A-1999 (alias x-IBM949C)", International Components for Unicode, Unicode Consortium. This is the ASCII-based version of IBM-949. http://icu4c-demos.unicode.org/icu-bin/convexp?conv=ibm-949_P11A-1999&s=ALL ↩

  28. International Components for Unicode (ICU), ibm-949_P110-1999.ucm, 2002-12-03 https://github.com/unicode-org/icu/blob/master/icu4c/source/data/mappings/ibm-949_P110-1999.ucm ↩

  29. "Coded character set identifiers: CCSID 949". IBM Globalization. IBM. Archived from the original on 2014-11-29. https://web.archive.org/web/20141129233846/http://www-01.ibm.com/software/globalization/ccsid/ccsid949.html ↩

  30. "IBM Korean Graphic Character Set: DBCS-Host and DBCS-PC" (PDF). IBM. 2001 [1992]. C-H 3-3220-125 1992-09. https://public.dhe.ibm.com/as400/products/clientaccess/win32/files/globalization/Korean_base1992.pdf ↩

  31. "Converter Explorer: ibm-949_P110-1999 (alias x-IBM949)", International Components for Unicode, Unicode Consortium http://icu4c-demos.unicode.org/icu-bin/convexp?conv=ibm-949_P110-1999&s=ALL ↩

  32. International Components for Unicode (ICU), ibm-949_P110-1999.ucm, 2002-12-03 https://github.com/unicode-org/icu/blob/master/icu4c/source/data/mappings/ibm-949_P110-1999.ucm ↩

  33. "Converter Explorer: ibm-949_P110-1999 (alias x-IBM949)", International Components for Unicode, Unicode Consortium http://icu4c-demos.unicode.org/icu-bin/convexp?conv=ibm-949_P110-1999&s=ALL ↩

  34. International Components for Unicode (ICU), ibm-949_P110-1999.ucm, 2002-12-03 https://github.com/unicode-org/icu/blob/master/icu4c/source/data/mappings/ibm-949_P110-1999.ucm ↩

  35. International Components for Unicode (ICU), ibm-949_P110-1999.ucm, 2002-12-03 https://github.com/unicode-org/icu/blob/master/icu4c/source/data/mappings/ibm-949_P110-1999.ucm ↩

  36. "2.0: Changes in Unicode 1.0" (PDF). The Unicode Standard, Version 1.1. Unicode Consortium. pp. 3–4. UTR #4. https://www.unicode.org/versions/Unicode1.1.0/ch02.pdf ↩

  37. "CPGID 01449: IBM default PUA". IBM Globalization: Code page identifiers. IBM. Archived from the original on 2015-09-16. IBM has designated 195 positions from U+F83D to U+F8FF for use as IBM Corporate-zone and intends to use them consistently within IBM whenever there is a need to maintain the round-trip integrity of IBM characters. https://web.archive.org/web/20150916190822/http://www-01.ibm.com/software/globalization/cp/cp01449.html ↩

  38. IBM (1997). unicode.nam: Allow the Unicode characters to be specified using either the IBM or PostScript like names. (Included with Borgendale, Ken, OS/2 Codepage and Keyboard Display Tools) /wiki/IBM ↩

  39. "IBM Korean Graphic Character Set: DBCS-Host and DBCS-PC" (PDF). IBM. 2001 [1992]. C-H 3-3220-125 1992-09. https://public.dhe.ibm.com/as400/products/clientaccess/win32/files/globalization/Korean_base1992.pdf ↩

  40. International Components for Unicode (ICU), ibm-949_P110-1999.ucm, 2002-12-03 https://github.com/unicode-org/icu/blob/master/icu4c/source/data/mappings/ibm-949_P110-1999.ucm ↩

  41. International Components for Unicode (ICU), ibm-949_P110-1999.ucm, 2002-12-03 https://github.com/unicode-org/icu/blob/master/icu4c/source/data/mappings/ibm-949_P110-1999.ucm ↩

  42. Private Use Area mapped hanja are identified from code charts. The IBM document C-H 3-3220-125 1992-09 gives code charts for the code pages used as the double-byte components for Code page 933 and an older version of Code page 949 without these extensions; however, the hanja in this section correspond to (and are in the same order as) the subset of table 7 for which a "PC Code" is not listed.[11] The Corporate Private Use Area mappings are also co-ordinated with other code pages,[19] including Code page 933,[21] which can be used to obtain the "Host Code" for a given Corporate Private Use Area mapping. /wiki/Code_page_933 ↩

  43. This is not included for IPA support. Rather, in Code page 933, SO 0x4160 is a not-equals sign displayed with a slash, while IBM-933 SO 0x418D is one displayed with a backslash (i.e. =⃥).[11] Although it is IBM-933 SO 0x4160 which is mapped to the usual not-equals GCGID SA540080 (fullwidth of SA540000), it is IBM-933 SO 0x418D which is mapped to EUC-KR and IBM-949 0xA1C1,[11] due to the reference glyph for the not-equals sign in KS C 5601-1987 also showing it with a backslash.[23] Hence, U+2260, which is mapped to EUC-KR and therefore IBM-949 0xA1C1, is mapped to IBM-933 SO 0x418D, leaving IBM-933 SO 0x4160 (and therefore IBM-949 0x9AA6) to be mapped to the visually similar character at U+01C2.[24] /wiki/Shift_Out ↩

  44. The mapping from IBM is U+5231 刱, but the glyph in the IBM document C-H 3-3220-125 1992-09 is closer to U+5259 剙 (host code 62D5).[11] https://en.wiktionary.org/wiki/%E5%89%99 ↩

  45. "IBM Korean Graphic Character Set: DBCS-Host and DBCS-PC" (PDF). IBM. 2001 [1992]. C-H 3-3220-125 1992-09. https://public.dhe.ibm.com/as400/products/clientaccess/win32/files/globalization/Korean_base1992.pdf ↩

  46. International Components for Unicode (ICU), ibm-949_P110-1999.ucm, 2002-12-03 https://github.com/unicode-org/icu/blob/master/icu4c/source/data/mappings/ibm-949_P110-1999.ucm ↩

  47. International Components for Unicode (ICU), ibm-949_P110-1999.ucm, 2002-12-03 https://github.com/unicode-org/icu/blob/master/icu4c/source/data/mappings/ibm-949_P110-1999.ucm ↩