Misplaced Pages

#234765

61-597: It is an extended modification of GB/T 2312-80 , and corresponds to the union of the mainland Chinese GB standards GB 6345.1 -86 and GB 8565.2 -88, with some further modification and extensions. A subset of the GB 6345.1 extensions are incorporated into GB 18030 , while GB 8565.2 serves as the mainland Chinese source reference for certain CJK Unified Ideographs . GB 6345.1-86 ( 32 × 32 Dot Matrix Font Set of Chinese Ideographs for Information Interchange ) includes both

122-541: A corrigendum and an extension for GB 2312. The corrigendum alters the following two characters: Deployed implementations incorporating GB 2312, such as Windows code page 936 , generally follow these corrections in mapping 79-81 to U+953A. The extension adds half-width ISO 646-CN characters in row 10 (in addition to the existing full-width characters in row 3) and extends the set of 26 non-ASCII pinyin characters in row 8 with six additional such characters. These GB 6345.1 extensions are also incorporated into GB/T 12345 ,

183-765: A Unicode Private Use Area code point (U+E000–F8FF) in GBK 1.0 and that have later been encoded in Unicode. This is specified in Appendix E of GB 18030. There are 24 characters in GB ;18030-2005 that are still mapped to Unicode PUA. In the GB 18030-2022 update, the requirements for characters to be mapped to PUA has been lifted completely and all characters should be mapped to their standard Unicode codepoints. Of these, 18 mappings were updated by position-swapping similar to what happened between GBK and GB 18030. The remaining six kept

244-548: A further amendment are to be made to GB 18030-2022 available for public consultation. The current draft updates up to Unicode 15.1 on Ideographic Description Characters , CJK Unified Ideographs URO, Extension A, B, C, G, H and I. Originally, in late 2022, it would have placed 897 new sinographic characters in Plane 10 ( hexadecimal : 0A), a yet-untitled astral Unicode plane , for citizen real-name certification in China, but eventually

305-466: A national counterpart to ASCII . Compare row 3 of KS X 1001 , which does the same with South Korea 's ISO 646 version, and row 3 of JIS X 0208 and of KPS 9566 , which include only the alphanumeric subset, but in the same layout. The following chart lists ISO 646-CN. When used in an encoding allowing combination with ASCII such as EUC-CN (and its superset GB 18030 ), these characters are usually implemented as fullwidth characters, hence mappings to

366-490: A non-mandatory standard. GB/T 2312-1980 was originally a mandatory national standard designated GB 2312-1980 . However, following a National Standard Bulletin of the People's Republic of China in 2017, GB 2312 is no longer mandatory, and its standard code is modified to GB/T 2312-1980 . GB/T 2312-1980 has been superseded by GBK and GB 18030 , which include additional characters, but GB/T 2312 remains in widespread use as

427-476: A range of values for the second byte of 0x30–0x39 (the ASCII codes for decimal digits). The first byte has the range 0x81 to 0xFE, as before. This means that a string-search routine that is safe for GBK should also be reasonably safe for GB18030 (in much the same way that a basic byte-oriented search routine is reasonably safe for EUC ). This gives a total of 1,587,600 (126×10×126×10) possible 4 byte sequences, which

488-447: A risk for misencoding as improper handling of text can result in missing information. To map the qūwèi code points to ISO-2022 bytes, add 32 ( 0x20 ) to both the row number (or qū, 区) and cell/column number (or wèi, 位). The result of addition to the row number of the code point will form the high byte, and the result of addition to the cell number of the code point will form the low byte similar to EUC encoding. For example, to encode

549-411: A subset of those encodings. As of September 2022 , GB2312 is the second-most popular encoding served from China and territories (after UTF-8 ), with 5.5% of web servers serving a page declaring it. Globally, GB2312 is declared on 0.1% of all web pages. However, all major web browsers decode GB2312-marked documents as if they were marked with the superset GBK encoding, except for Safari and Edge on

610-544: Is a Chinese government standard , described as Information Technology — Chinese coded character set and defines the required language and character support necessary for software in China . GB18030 is the registered Internet name for the official character set of the People's Republic of China (PRC) superseding GB2312 . As a Unicode Transformation Format (i.e. an encoding of all Unicode code points), GB18030 supports both simplified and traditional Chinese characters . It

671-484: Is a data file which was previously provided by the Unicode Consortium , although it has been designated as obsolete since August 2011 and is no longer hosted as of September 2016. As of 2015, Microsoft .Net Framework follows GB 18030 mappings when mapping those two characters in data labelled gb2312 , whereas ICU , iconv-1.14, php-5.6, ActivePerl-5.20, Java 1.7 and Python 3.4 follow GB2312.TXT in response to

SECTION 10

#1732880812235

732-662: Is also compatible with legacy encodings including GB/T 2312 , CP936 , and GBK  1.0. The Unicode Consortium has warned implementers that the latest version of this Chinese standard, GB 18030-2022 , introduces what they describe as "disruptive changes" from the previous version GB 18030-2005 "involving 33 different characters and 55 code positions". GB 18030-2022 was enforced from 1 August 2023. It has been implemented in ICU 73.2; and in Java 21, and backported to older Java 8, 11, 17 (LTS releases) and 20.0.2. In addition to

793-477: Is basically an extension based on GBK with additional characters in CJK Unified Ideographs Extension A. The second version designated GB 18030-2005 Information Technology—Chinese coded character set has the same mandatory subset as GB 18030-2000 of 1-, 2- and 4-byte encodings. This version also includes the full CJK Unified Ideographs Extension B in the 4-byte encoding section which

854-522: Is easily sufficient to cover Unicode 's 1,112,064 (17×65536 − 2048 surrogates) assigned, reserved, and noncharacter code points. Unfortunately, to further complicate matters there are no simple rules to translate between a 4 byte sequence and its corresponding code point . Instead, codes are allocated sequentially (with the first byte containing the most significant part and the last the least significant part) only to Unicode code points that are not mapped in any other manner. For example: An offset table

915-539: Is encoded over GR, both bytes have the eighth bit set (i.e. are greater than 0x7F). GBK and GB 18030 also make use of two-byte codes in which only the first byte has the eighth bit set for extension purposes: such codes are outside of the GB/T 2312 plane, and are not tabulated here. This chart details the overall layout of the main plane of the GB/T 2312 character set by lead byte. For lead bytes used for characters other than hanzi , links are provided to charts on this page listing

976-417: Is often used as the character encoding (i.e. for external storage) in programs that deal with GB/T 2312, thus maintaining compatibility with ASCII . Two bytes are used to represent every character not found in ASCII . The value of the first byte is from 0xA1–0xF7 (161–247), while the value of the second byte is from 0xA1–0xFE (161–254). Since all of these ranges are beyond ASCII, like UTF-8, it

1037-456: Is outside the BMP as a suggestion support requirement. However, as the inclusion of CJK Unified Ideographs Extension B in a 4-byte region is required to be maintained during information processing, software can no longer get away with treating characters as 16-bit fixed width entities ( UCS-2 ). Therefore, they must either process the data as a variable-width format (as with UTF-8 or UTF-16 ), which

1098-503: Is possible to check if a byte is part of a multi-byte construct when using EUC-CN, but not if a byte is first or last. Compared to UTF-8 , GB/T 2312 (whether native or encoded in EUC-CN) is more storage efficient: while UTF-8 uses three bytes per CJK ideograph , GB/T 2312 only uses two. However, GB/T 2312 does not cover as many ideographs as Unicode does. To map the qūwèi code points to EUC bytes, add 160 ( 0xA0 ) to both

1159-456: Is the earliest font template based on GB/T 2312 that features corrections and extensions including: GB/T 2312 did not have corrections, but these corrections are included in font templates that are based on GB/T 2312 including GB/T 12345; its supersets GBK and GB 18030 also included these corrections. GB/T 2312 is also used in ISO-IR-165 . GB 18030 GB 18030

1220-486: Is the most common choice, or move to a larger fixed-width format (i.e. UTF-32 ). Microsoft made the change from UCS-2 to UTF-16 with Windows 2000. This version matches with Unicode 3.1, and also provided support for Hangul ( Korean ), Mongolian (including Manchu , Clear script , Sibe hergen , Galik ), Tai Nuea , Tibetan , Uyghur / Kazakh / Kyrgyz and Yi . The third and latest version, GB 18030-2022 Information Technology—Chinese coded character set , mandates

1281-646: Is used in the WHATWG and W3C version of GB 18030 to efficiently translate code points. ICU and glibc use similar range definitions to avoid wasting space on large sequential blocks. GB   18030 has been supported on Windows since the release of Windows 95 , as code page 54936. Windows 2000 and XP offer a GB18030 Support Package. The open source PostgreSQL database supports GB18030 through its full support for UTF-8, i.e. by converting it to and from UTF-8. Similarly Microsoft SQL Server supports GB18030 by conversion to and from UTF-16. More specifically, supporting

SECTION 20

#1732880812235

1342-531: The gb2312 label. Ruby 2.2 is compatible with both implementations; it internally converts the conflictive characters to the GB 18030 subset. The W3C / WHATWG technical recommendation for use with HTML5 specifies a GBK encoding to be inferred for streams labelled gb2312 , which in turn uses a GB18030 decoder. Other differing mappings have been defined and used by individual vendors, including one from Apple . This row contains punctuation, mathematical operators, and other symbols. The following table shows

1403-462: The BMP . These parts are fully mandatory in GB 18030-2000. Most major computer companies had already standardized on some version of Unicode as the primary format for use in their binary formats and OS calls. However, they mostly had only supported code points in the BMP originally defined in Unicode 1.0, which supported only 65,536 codepoints and was often encoded in 16 bits as UCS-2 . This standard

1464-533: The Cyrillic script , sufficient to write the modern Russian alphabet and Bulgarian alphabet , although other forms of Cyrillic require additional letters. Compare with row 7 of JIS X 0208 , which this row matches, and with row 12 of KS X 1001 and row 5 of KPS 9566 , which use the same layout but in different rows. This row contains bopomofo and pinyin characters, excluding ASCII letters (which are in row 3). The highlighted characters are those which are not in

1525-567: The Greek and Cyrillic alphabets , Zhuyin , and a double-byte set of Pinyin letters with tone marks. In later version GB/T 2312-1980, there are 7,445 letters. Characters in GB/T ;2312 are arranged in a 94×94 grid (as in ISO ;2022 ), and the two-byte code point of each character is expressed in the qūwèi ( 区位 ) form, which specifies a row ( 区 ; qū ) and the position of the character within

1586-595: The Halfwidth and Fullwidth Forms block are used as shown below. GB 6345.1 also handles this row as fullwidth, and adds the halfwidth forms (as above) as row 10. Apple mostly maps this row to fullwidth code points as below, but uses non-fullwidth mappings for the overline and yuan sign as above. This set contains Hiragana for writing the Japanese language . Compare with row 4 of JIS X 0208 , which this row matches, and with row 10 of KS X 1001 and of KPS 9566 , which use

1647-481: The Traditional Chinese counterpart to GB 2312, in addition to 29 vertical presentation forms in row 6. Later GB/T 6345.1-2010 published in 2011 officially adds half-width forms of the 32 pinyin characters (including the six new additions) in row 8 to row 11. This addition is not featured in GB 18030. The six additional pinyin characters from GB 6345.1 and the vertical presentation forms from GB 12345 — but not

1708-502: The Unihan database. In total the set contains 8446 characters. A number of patterned semigraphic characters are included in row 6. This collides with the vertical presentation forms included in other extensions such as Mac OS Simplified Chinese and GB 18030. The GB 6345.1 corrections to GB 2312 are applied, but two Unicode mappings are reversed compared to other encodings which include GB 2312 with GB 6345.1 extensions. The table below shows

1769-467: The interpunct ( Chinese : 间隔点 ; lit. 'separator dot') and em dash ( Chinese : 破折号 ) in the subset of GBK and GB 18030 corresponding to GB/T 2312 ( U+00B7 · MIDDLE DOT and U+2014 — EM DASH ) differ from those which are listed in GB2312.TXT ( U+30FB ・ KATAKANA MIDDLE DOT and U+2015 ― HORIZONTAL BAR ), which

1830-754: The repertoire (reduced to 622 characters after expert review) was fast-tracked into Unicode 15.1 in September 2023, as the CJK Unified Ideographs Extension I block. Following this, the amendment draft was modified to use the Extension I code points. GB 18030 defines a one (ASCII), two (extended GBK), or four-byte (UTF) encoding. The two-byte codes are defined in a lookup table, while the four-byte codes are defined sequentially (hence algorithmically) to fill otherwise unencoded parts in UCS . GB 18030 inherits

1891-463: The GB 18030 mappings for these GB/T 2312 characters first, followed by any other documented mappings. This row contains various types of list marker. Lowercase forms of the Roman numerals were not included in the original GB/T 2312 nor in GB/T 12345, but are included in both Windows code page 936 and GB 18030 . A euro sign was also added by GB 18030. This row contains ISO 646-CN (GB/T 1988-80),

ISO-IR-165 - Misplaced Pages Continue

1952-615: The GB 2312 corrections from GB 6345.1, but not its extensions. The Unihan database references GB 8565.2 as the mainland Chinese source of several hanzi included in Unicode . Its Unihan source abbreviation is G8 . ISO-IR-165 incorporates the GB 2312 extensions from both GB 6345.1-86 and GB 8565.2-88. Additionally, it adds 161 further characters (including 139 hanzi, identified as “general Chinese characters and variants”). These CCITT hanzi extensions have on occasion been mistaken for standard GB 8565.2 characters, including in previous revisions of

2013-555: The GB18030 encoding on Windows means that Code Page 54936 is supported by MultiByteToWideChar and WideCharToMultiByte . Due to the backward compatibility of the mapping, many files in GB18030 can be actually opened successfully as the legacy Code Page 936, that is GBK, even if the Code Page 54936 is not supported. However, that is only true if the file in question contains only GBK characters. Loading will fail or cause corrupted result if

2074-414: The appearance of CJK Unified Ideographs Extension B. Some characters used by ethnic minorities in China , such as Mongolian characters and Tibetan characters ( GB 16959 -1997 and GB/T 20542 -2006), have been added as well, which accounts for the renaming of the standard. Compared with its ancestors, GB 18030's mapping to Unicode has been modified for the 81 characters that were provisionally assigned

2135-422: The bad aspects of GBK , most notably needing special code to safely find ASCII characters in a GB18030 sequence. The one- and two-byte code points are essentially GBK with the euro sign, PUA mappings for unassigned/user-defined points, and vertical punctuations. The four byte scheme can be thought of as consisting of two units, each of two bytes. Each unit has a similar format to a GBK two byte character but with

2196-473: The base GB 2312 set but are added by GB 6345.1 , and also included in GB/T 12345, Windows code page 936 , Mac OS Simplified Chinese and GB 18030. They are seen as "standard extensions to GB 2312". GB 6345.1 treats the pinyin in this row as fullwidth, and includes halfwidth counterparts as row 11; GB 18030 does not do this. GB 5007.1-85 24×24 Bitmap Font Set of Chinese Characters for Information Exchange ( Chinese : 信息交换用汉字 24x24 点阵字模集 )

2257-539: The basic set", was published on March 17, 2000. The encoding scheme stays the same in the new version, and the only difference in GB-to-Unicode mapping is that GB 18030-2000 mapped the character A8 BC (ḿ) to a private use code point U+E7C7, and character 81 35 F4 37 (without specifying any glyph) to U+1E3F (ḿ), whereas GB 18030-2005 swaps these two mapping assignments. More code points are now associated with characters due to update of Unicode , especially

2318-604: The beginning and end of a range of GB 2312 text differ. In the tables below, where a pair of hexadecimal numbers is given for a prefix byte or a coding byte, the smaller (with the eighth bit unset or unavailable) is used when encoded over GL ( 0x 21-0x7E), as in ISO-2022-CN or HZ-GB-2312 , and the larger (with the eighth bit set) is used in the more typical case of it being encoded over GR (0xA1-0xFE), as in EUC-CN , GBK or GB 18030 . Qūwèi numbers are given in decimal. When GB/T 2312

2379-501: The cell number 66: 66+160=226= 0xE2 . So, the full encoding is <CD E2> . ISO-2022-CN is another encoding form of GB/T 2312, which is also the encoding specified in the official documentation. This encoding references the ISO-2022 standard, which also uses two bytes to encode characters not found in ASCII. However, instead of using the extended region of ASCII, ISO-2022 uses

2440-464: The character "外" at qūwèi cell 45-66, the high byte will use the row number 45: 45+32=77= 0x4D , and the low byte will come from the cell number 66: 66+32=98= 0x62 . So, the full encoding is <4D 62> . HZ is another encoding of GB/T 2312 that is used mostly for Usenet postings; characters are represented with the same byte pairs as in ISO-2022-CN, but the byte sequences denoting

2501-487: The characters in Unicode 2.1 plus new characters found in the Unicode CJK Unified Ideographs Extension A block although, despite its name, it does not contain glyphs for all characters encoded by GB 18030, as all (about a million) Unicode code points up to U+10FFFF can be encoded as GB 18030. GB 18030 compliance certification only requires correct handling and recognition of glyphs in

ISO-IR-165 - Misplaced Pages Continue

2562-560: The characters encoded under that lead byte. For lead bytes used for hanzi, links are provided to the appropriate section of Wiktionary 's hanzi index. The following charts list the non- hanzi characters available in GB/T 2312, in GB/T 12345, and in double-byte region 1 of GB 18030 (which roughly corresponds to the non-hanzi region of GB/T 2312). Notes are made where these differ, and where GB 6345.1 and ISO-IR-165 differ from these. Cross-references are made to articles on other CJK national character sets for comparison. Unicode mappings of

2623-494: The code positions used for the vertical extensions. Compare with row 6 of JIS X 0208 , which this row matches when the vertical forms are not included, and with row 6 of KPS 9566 , which includes the same Greek letters in the same layout, but adds Roman numerals rather than vertical forms. Contrast row 5 of KS X 1001 , which offsets the Greek letters to include the Roman numerals first. This set includes both cases of 33 letters from

2684-448: The encoding is a full UTF). The standard is known to support English/ASCII and the "following non-Chinese scripts are recognized by GB 18030-2022: Arabic, Tibetan, Mongolian, Tai Le, New Tai Lue, Tai Tham, Yi, Lisu, Hangul (Korean), and Miao." The GB18030 Support Package for Windows contains SimSun18030.ttc, a TrueType font collection file which combines two Chinese fonts, SimSun-18030 and NSimSun-18030. The SimSun 18030 font includes all

2745-682: The encoding method, this standard contains requirements about which additional scripts and languages should be represented, and to whom this standard is applicable. This standard however does not define the official character forms for the Chinese characters; this is standardised in List of Commonly Used Standard Chinese Characters . The GB18030 character set is formally called "Chinese National Standard GB 18030-2005: Information Technology—Chinese coded character set". GB abbreviates Guójiā Biāozhǔn (国家标准), which means national standard in Chinese. The standard

2806-663: The file contains characters that do not exist in GBK (see § Technical details for examples). GNU glibc 's gconv, the character codec library used on most Linux distributions, supports GB 18030-2000 since 2.2, and GB 18030-2005 since 2.14; glibc notably includes non-PUA mappings for GB 18030-2005 in order to achieve round-trip conversion. GNU libiconv , an alternative iconv implementation frequently used on non-glibc UNIX-like environments like Cygwin , supports GB 18030 since version 1.4. As of 2022, "supporting non-Chinese scripts continues to be optional" (presumably for display/font support only; and in China, since

2867-609: The half-width forms — are included in the classic Mac OS encoding for Simplified Chinese (a modification of EUC-CN ), and also as two-byte codes in GB 18030 . The additional pinyin characters are as follows: These extensions and modifications to GB 2312 were first introduced in GB 5007.1-85 in 1985. GB 8565.2-88 ( Information Processing - Coded Character Sets for Text Communication - Part 2: Graphic Characters ) defines an extension for GB 2312, adding 705 characters between rows 13–15 and 90–94, of which 69 (all in row 15) are non-hanzi. It includes

2928-429: The label GB_2312 . There is an analogous character set known as GB/T 12345 Code of Chinese ideogram set for information interchange supplementary set , which supplements GB/T 2312 with traditional character forms by replacing simplified forms in their qūwèi code, and some extra 62 supplemental characters. GB-encoded fonts often come in pairs, one with the GB/T 2312 (simplified) character set and

2989-471: The mandatory (two-byte, and CJK Ext. A) Chinese part. Nevertheless, the requirement of PUA characters in the standard have hampered this implementation. Microsoft YaHei and DengXian provided by Microsoft are updated in 2023 to match GB 18030-2022 implementation level 2, and SimSun is updated to match implementation level 3. Source Han Sans (and its counterpart Noto Sans CJK) are already compliant with GB 18030-2022 implementation level 2 when

3050-480: The mappings and their corresponding glyphs including GB 18030 : GB 2312 GB/T 2312-1980 is a key official character set of the People's Republic of China , used for Simplified Chinese characters . GB2312 is the registered internet name for EUC-CN , which is its usual encoded form. GB refers to the Guobiao standards (国家标准), whereas the T suffix ( 推荐 ; tuījiàn ; 'recommendation') denotes

3111-438: The other with the GB/T 12345 (traditional) character set. There exists more GB supplementary encoding sets that supplements GB/T 2312, including GB/T 7589 Code of Chinese ideograms set forinformation interchange--The 2nd supplementary set and GB/T 7590 Code of Chinese ideograms set forinformation interchange--The 4th supplementary set which provides additional [Variant Chinese characters|variant characters] in

SECTION 50

#1732880812235

3172-434: The requirement of "all products using this standard should implements Implementation Level 1" that includes 66 new BMP characters in the 4-byte encoding region that were added between Unicode 3.1 and Unicode 11.0. Implementation Level 2 requires the support of List of Commonly Used Standard Chinese Characters , and Implementation Level 3 requires all other specified regions in the standard. From late 2022 to 2023, drafts of

3233-463: The row (cell; 位 ; wèi ). (This structure is the same as used by other ISO-2022-based national CJK character set standards; compare kuten .) For example, the character "外" (meaning: foreign) is located in row 45 position 66, thus its qūwèi code is 45-66. The rows (numbered from 1 to 94) contain characters as follows: The rows 10–15 and 88–94 are unassigned. For GB/T 2312-1980, it contains 682 signs and 6763 Chinese Characters. EUC-CN

3294-400: The row number (or qū, 区) and cell/column number ( ten or wèi, 位). The result of addition to the row number of the code point will form the high byte, and the result of addition to the cell number of the code point will form the low byte. For example, to encode the character "外" at qūwèi cell 45-66, the high byte will use the row number 45: 45+160=205= 0xCD , and the low byte will come from

3355-516: The same qūwèi encoding format (later used in ISO-2022-CN), but has no relation with characters encoded in GB/T 2312. While GB/T 2312 covers over 99.99% contemporary Chinese text usage, historical texts and many names remain out of scope. Old GB 2312 standard includes 6,763 Chinese characters (on two levels: the first is arranged by reading, the second by radical then number of strokes), along with symbols and punctuation, Japanese kana ,

3416-455: The same byte range as ASCII: the value of the first byte is from 0x21–0x77 (33–119), while the value of the second byte is from 0x21–0x7E (33–126). As the byte range overlaps ASCII significantly, special characters are required to indicate whether a character is in the ASCII range or is part of the two-byte sequence of extended region, namely the Shift Out and Shift In functions. This poses

3477-646: The same layout, but in a different row. This row contains basic support for the modern Greek alphabet , without diacritics or the final sigma . The highlighted characters are presentation forms of punctuation marks for vertical writing, and are not included in GB/T 2312 proper, but are included in this row by GB/T 12345, Windows code page 936 , Mac OS Simplified Chinese, and GB 18030. They are seen as "standard extensions to GB 2312". Conversely, ISO-IR-165 includes patterned semigraphic characters in this row (mostly without exact counterparts in Unicode), colliding with

3538-462: 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 in GB/T 2312, although it is added in GBK and GB 18030 outside of the main GB/T 2312 plane, at 0xA960. Compare with row 5 of JIS X 0208 , which this row matches, and with row 11 of KS X 1001 and of KPS 9566 , which use

3599-428: The suggestion support part of CJK Unified Ideographs Extension B in GB 18030-2005, along with updates up to Unicode 11.0 including Kangxi Radicals and CJK Unified Ideographs URO , Extension C, D, E and F. Additional languages are also recognized by GB 18030-2022 such as part of Arabic , Tai Le , New Tai Lue , Tai Tham , Lisu , and Miao . GB 18030-2022 also introduces three implementation levels, with

3660-547: The two-byte PUA mappings, so that a change to the 4-byte sequence is needed to follow the non-PUA preference. The first version of GB 18030, designated GB 18030-2000 Information Technology—Chinese coded character set for information interchange — Extension for the basic set , consists of 1-byte and 2-byte encodings, together with 4-byte encoding for CJK Unified Ideographs Extension A matching those in Unicode 3.0. The corresponding Unicode code points of this subset, including provisional private assignments, lie entirely in

3721-535: Was published by the China Standard Press, Beijing, 8 November 2005. Only a portion of the standard is mandatory. Since 1 May 2006, support for the mandatory subset is officially required for all software products sold in the PRC. An older version of the standard, known as "Chinese National Standard GB 18030-2000: Information Technology—Chinese ideograms coded character set for information interchange—Extension for

SECTION 60

#1732880812235
#234765