Kbase P93919: Slick-edit Appbuilder editor not working in OpenEdge 10.0B for UTF-8 client
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
2/26/2010 |
|
Status: Verified
SYMPTOM(s):
Slick-edit Appbuilder editor not working in OpenEdge 10.0B for UTF-8 client
Procedure Editor is started with -cpinternal UTF-8 -cpstream UTF-8
Progress key words entered in lowercase like DEFINE, DISPLAY, FOR EACH don't convert to uppercase.
Progress key words entered in lowercase like DEFINE, DISPLAY, FOR EACH do not change color
If Progress keywords are entered in UPPERCASE they are correctly color coded
If the keyword case is set to lowercase, capitalized keywords are converted to UPPERCASE as each letter is entered
FACT(s) (Environment):
OpenEdge 10.0B
OpenEdge 10.1x
OpenEdge 10.2A
OpenEdge Category: Language (4GL/ABL)
Windows
CAUSE:
Bug# OE00109049
CAUSE:
The problem is purely cosmetic and although the editor keyword and casing in the source code isn't correct the client will behave correctly in all other aspects.
FIX:
None at this time.
This is a Development session issue and it is assumed that the UTF-8 client is being used primarily to create UTF-8 r-code. If this is the case then there are two possible ways to work around this problem:
1. Use a single byte code page session and -cprcodeout UTF-8 to create UTF-8 r-code. For example:
prowin32.exe -cpinternal 1252 -cpstream 1252 -cpcoll basic -cprcodeout UTF-8
This method will create UTF-8 r-code but it will only work if the source code contains only ASCII characters in the range 0 - 127. If there are any extended characters (range 128 - 255) in the source such as the Euro, Pound Sterling, French accented characters, German umlaut characters etc, then the compile will fail and the result will be error 8774 (See solution P36438).
2. Use a sinlge byte session to edit and Develop the code in the Appbuilder, ensuring that the keyword casing and color coding is correct. Then use a second UTF-8 client session to compile. For example, the Development session could start with:
prowin32.exe -cpinternal 1252 -cpstream 1252 -cpcoll basic
Then start a session to use the compiler with:
prowin32.exe -cpinternal UTF-8 -cpstream 1252 -cpcoll basic
This will compile the source code creating UTF-8 r-code, while preserving the keyword casing and color coding of the source.