Kbase P155203: logical fields with UTF-8 extended character formats are corrupted on display
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
30/10/2009 |
|
Status: Unverified
SYMPTOM(s):
Logical field with extended character format displays wrong value
If a logical fields has a non YES/NO format, and that format contains a UTF-8 extended character (e.g. 'jä
o'), then the field can be corrupted when displayed.
For example a field defined in a browse as:
ttTest.Logical1 COLUMN-LABEL 'log1' FORMAT 'jä
o' width 20
Displays as "j@Testst". The display has been corrupted by some other text string value.
FACT(s) (Environment):
The session is using the unicode client started with -cpinternal UTF-8 -cpstream UTF-8
The source code contains UTF-8 mutli byte extended characters.
OpenEdge 10.1x
OpenEdge 10.2x
Windows
CAUSE:
Bug# OE00192714
FIX:
None at this time.
As a work around add a space after the extended character in the source code. For example:
ttTest.Logical1 COLUMN-LABEL 'log1' FORMAT 'jä
o' width 20
The display will now work correctly and only display either 'jä' or 'no'.