Try OpenEdge Now
skip to main content
Internationalizing Applications
Using Multi-byte Code Pages : Issues specific to multi-byte code pages : OpenEdge support for multi-byte code pages : Additional GB18030 code page considerations
Additional GB18030 code page considerations
When working with the GB18030 code page, consider the following:
*The GB18030 code page is a multi-byte code page, consisting of one-, two-, and four-byte characters, that extends the GB2312 code page and includes all characters defined in Unicode. Unlike most multi-byte code pages that OpenEdge supports, you cannot use the lead byte of multi-byte characters in the GB18030 code page to determine the character's length. OpenEdge uses the International Components for Unicode (ICU) library to convert characters between the GB18030 code page and Unicode within the OpenEdge GUI client.
*OpenEdge supports the GB18030 code page, primarily, for file input and output. More specifically, you can use the GB18030 code page for the following:
*In settings for the -cpstream, -cplog, and -cpprint startup parameters
*With any ABL CONVERT SOURCE/TARGET phrase that applies to files, for example:
COPY-LOB FROM FILE "gb.txt" TO myunicodeclob
*With the ASC, CHR, and CODEPAGE-CONVERT functions (but if used as the target code page of CHR or CODEPAGE-CONVERT, you cannot use the resulting character or character string in ABL)
*With file input and output in the SQL products
*You cannot use the GB18030 code page in the following instances:
*In other ABL statements (not listed above)
*As a CLOB or LONGCHAR code page
*In settings for the -cpinternal, -cpterm, -cprcodein, or -cprcodeout startup parameters
*As a database code page
*With the PROUTIL db-name -C CONVCHAR CONVERT command (although it can be used for CONVCHAR ANALYZE)