Kbase P146383: Translation Manager: Why are the ALERT-BOX button labels are not being translated?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/15/2009 |
|
Status: Unverified
GOAL:
Translation Manager: Why are the ALERT-BOX button labels are not being translated?
GOAL:
Can the default button labels be translated using the Translation Manager?
GOAL:
How can we translate the labels of the buttons in our application using the Translation Manager?
FACT(s) (Environment):
Windows
Progress 8.x
Progress 9.x
OpenEdge 10.x
FIX:
There are two types of buttons in Progress / OpenEdge 4GL / ABL:
1. The default buttons: These are the buttons supplied by the AppBuilder at design time, like the OK, DONE, CANCEL, etc buttons as well as the ALERT-BOX buttons created by the MESSAGE statement, like YES-NO, YES-NO-CANCEL, OK, etc. The labels of these default buttons are supplied by the Windows Operating System and hence are not translatable.
2. The user defined buttons: These are the buttons created by the DEFINE BUTTON or CREATE BUTTON statements. The labels of the user defined buttons are supplied by the developer and hence are translatable.
When creating Windows applications, developers often use the default buttons. This technique is not recommended for applications slated for translation into multiple languages because the labels of the default buttons labels are supplied by Windows, are non translatable and are always displayed in the language of the Operating System. For example, if an application is running under the French Windows Operating System, the default buttons labels appear in French.
Use the default buttons only if the application will always run under one Operating System Language environment. Avoid using the default buttons if the application will be translated to multiple languages or if it will run under more than one Operating System Language environment.