Progress
Language Reference
CODEPAGE-CONVERT Function
Converts a string value from one code page to another.
SYNTAX
source-string
A character expression to be converted.
target-codepage
A character-string expression that evaluates to the name of a code page. The name that you specify must be a valid code page name available in the
DLC/convmap.cp
file (a binary file that contains all of the tables that Progress uses for character management). If you supply a non-valid name, the CODEPAGE-CONVERT function returns the unknown value (?). Before returning a character value, the CODEPAGE-CONVERT function converts source-string from source-codepage to target-codepage. The returned character value is relative to target-codepage. If you do not specify target-codepage, no code page conversions occur.source-codepage
A character-string expression that evaluates to the name of a code page. The name that you specify must be a valid codepage name available in the
EXAMPLEDLC/convmap.cp
file. If you supply a non-valid name, the CODEPAGE-CONVERT function returns the unknown value (?). The source-codepage specifies the name of the code page to which source-string is relative. The default value of source-codepage is the value of CHARSET attribute of the SESSION handle.This example assumes that the native code page of
r-codpag.p
is ibm850. It is written so that its embedded text strings are always converted to the internal code page of the Progress session (SESSION:CHARSET).
NOTES
- The CODEPAGE-CONVERT function returns the corresponding character string in the specified code page. By default, the value of SESSION:CHARSET is iso8859-1. You can set a different internal code page by specifying the Internal Code Page (-cpinternal) parameter. For more information, see the Progress Internationalization Guide and the Progress Startup Command and Parameter Reference.
- This function is especially useful if you plan to run a procedure in a Progress session in which the SESSION:CHARSET code page is different from the native code page of the procedure.
- When you write procedures with the Progress 4GL, you must use 7-bit (that is, ASCII) characters for field names and variable names. But you can use 8-bit and multi-byte characters, including Unicode, for data values such as character strings and constants. Thus, a procedure written and compiled on a system using one code page can be run on a system using another code page as long as you convert all embedded character strings to the internal code page. Using CODEPAGE-CONVERT as shown in the example allows your procedures to be virtually code page independent.
SEE ALSO
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |