Kbase P105096: What are the advantages of using the Unicode UTF-8 client in OpenEdge 10?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
27/01/2010 |
|
Status: Unverified
GOAL:
What are the advantages of using the Unicode UTF-8 client in OpenEdge 10?
GOAL:
What advantages does the Unicode client have over Progress version 9.1x?
GOAL:
What are the advantages of using UTF-8?
GOAL:
Is it necessary to maintain multiple sets of r-code when using UTF-8?
FACT(s) (Environment):
Progress 9.1x
OpenEdge 10.x
FIX:
In Progress version 9.1x, deployments are limited as follows:
1. Database and broker can be UTF-8, so can store data from many clients.
2. Clients must have a local code page to enter and store data in their native language (e.g. 1252 or iso8859-1 for Western European clients, 1250 or iso8859-2 for Central European clients).
3. Application code must not allow clients from incompatible regions (e.g iso8859-1 and iso8859-2) to access and update data entered by clients in the other region. If the application does not prevent this then corruption is likely to occur. So an iso8859-1 client cannot display and update data entered by an iso8859-2 client.
4. You will need multiple sets of r-code, one for each region since the local code page is stored in the r-code.
If you upgrade to OpenEdge 10 the GUI (only) Unicode client is available and this resolves the above problems by providing:
1. A UTF-8 client. The same client across all deployments regardless of region.
2. Any client can update any set of data entered into a UTF-8 database.
3. One single set of UTF-8 r-code to deploy to all regions.