Kbase P61002: International characters are not displayed properly after ch
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
21/01/2004 |
|
Status: Unverified
FACT(s) (Environment):
Progress 9.1D
FACT(s) (Environment):
Windows NT 32 Intel/Windows 2000
SYMPTOM(s):
International characters are lost when opening code within the AppBuilder
Extended characters are not displayed properly when opening code within the AppBuilder.
Extended characters are not displayed properly within the application after changing the -cpstream parameter.
Source code was previously compiled using -cpinternal ISO8859-1 and -cpstream IBM850.
Code can be opened without problems.
CHANGE:
Changed -cpstream to Latin1 (ISO8859-1 or 1252) and recompiled source code.
CAUSE:
In the beginning -cpstream ibm850 was used, so the source code (.w) and it's characters were saved/converted to ibm850 codepage. When previously opening the .w files it used the -cpstream again to properly convert the characters and display them properly as ISO8859-1. Now even though the codepage in the r-code is set as ISO8859-1 (because the default value is the same as -cpinternal), you basically get what you see. With this we mean that it saves the characters in the r-code as you see them on screen. So opening your .w file using your new parameter -cpstream ISO8859-1 (which displays incorrect characters on screen) and then saving this as .w and .r will result into wrong characters being saved as well, because it saves what you see.
FIX:
Use the toisol1.exe utility which is located in the %DLC%\Bin folder:
toisol1.exe [your old procedure].w > [new procedure].w
This will convert your source code codepage from IBM850 to ISO8859-1.
The last step is to recompile your application.