Kbase P142405: -useOsLocale does not work with UTF-8 client and No Break Space separator
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
4/14/2009 |
|
Status: Unverified
SYMPTOM(s):
-useOsLocale does not work with UTF-8 client and No Break Space separator
Numbers do not display as expected in Procedure Editor
ASC(SESSION:NUMERIC-SEPARATOR) returns unknown value (-1)
While entering numeric digits some digits overwrite those typed earlier. For example entering "12345" results in "1235" - the '4' has been overwritten by the '5'..
FACT(s) (Environment):
Session started with the startup parameter -useOsLocale
The client session is a Unicode UTF-8 GUI client.
Windows Regional Settings are configured for Scandinavian (e.g. Swedish, Norwegian, Finnish).
The Windows region default for Digit grouping symbol is blank - which is actually NBSP (NO-BREAK-SPACE).
Windows
OpenEdge 10.1x
CAUSE:
Bug# OE00182990
FIX:
None at this time.
As a workaround, either:
1. Use a comma as a separator.
prowin32.exe -cpinternal UTF-8 -cpstream UTF-8 -useOsLocale -numsep 44 -numdec 46
2. Use a normal space as a separator:
prowin32.exe -cpinternal UTF-8 -cpstream UTF-8 -useOsLocale -numsep 32
3. In a startup procedure use code similar to the following to reset the numeric separator:
IF ASC(SESSION:NUMERIC-SEPARATOR) = -1 THEN
SESSION:SET-NUMERIC-FORMAT(" ":U, SESSION:NUMERIC-DECIMAL-POINT).