Kbase P61800: I18N. Unicode and double-byte support in Progress OpenEdge 10
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/10/2008 |
|
Status: Unverified
GOAL:
I18N. Unicode and double-byte support in Progress OpenEdge 10
FIX:
Extracted from OpenEdge Development: Internationalizing Applications:
You can use multi-byte characters in every configuration OpenEdge supports, including client/server and batch. You are limited only by the multi-byte support provided by individual OpenEdge products.
Multi-byte characters are supported by the majority of the OpenEdge products - see below:
AppBuilder:
- Except for the Character Run window - supports double-byte and UTF-8 characters.
- Widgets created with the AppBuilder can have double-byte or UTF-8 characters in labels and in text.
- The Character Run window does not support double-byte or UTF-8 characters.
AppServer:
- Supports double-byte and UTF-8 characters.
Application Compiler:
- supports double-byte and UTF-8 characters. That is, the 4GL source code that the Application Compiler compiles can contain double-byte and UTF-8, and the resulting r-code supports double-byte and UTF-8 characters.
Graphical client:
- supports double-byte and UTF-8 characters.
Character client:
- The UNIX character client supports double-byte characters but not UTF-8 characters
- The Windows character client does not support multi-byte characters.
Batch client: (started with the command prowin32 -b)
- supports multi-byte characters
Data Dictionary:
- supports multi-byte characters
Data Servers:
- The DataServer for Oracle supports double-byte characters if the ORACLE DBMS is set up for Native Language Support (NLS). For more information on NLS, see the Oracle documentation.
- The DataServer for Oracle does not support UTF-8.