This release introduces a new mechanism for handling multilingual resources in the following runtime modules:
-
PowerBuilder Runtime files
-
Cloud App Launcher (Developers can choose which language to use for both installation and runtime. Please see the section called “Customizing and uploading cloud app launcher” in Users Guide for more details.)
Currently, the following runtime module does NOT support multilingual resources:
-
PowerServer Web APIs
The messages returned from PowerServer Web APIs will display in English (for EN version) or Japanese (for JP version).
How to support multilingual resources in PowerBuilder runtime files
Text resources previously embedded directly in runtime DLLs are now separated into independent .lng language package files, enabling runtime language switching and simplified localization without recompiling the runtime.
Each supported language is stored in a dedicated
.lng file (e.g., english.lng,
french.lng, japanese.lng). A
custom.lng file is provided for user-defined translations
and initially contains the same content as english.lng.
At least english.lng must be available for proper runtime
display.
-
.lng files are located in the runtime language folder, for example, C:\Program Files (x86)\Appeon\Common\PowerBuilder\Runtime 25.1.0.6180\lang. They will be packaged into the runtime installer later.
-
Only one custom language file is allowed, named
custom.lng. -
The file content format is
TextID, TextDescription. Keep the text IDs identical to the original package; edit only the text descriptions.
How to package the language file
The PowerBuilder Runtime Packager allows
you to select which language packages to include in the deployment.
For the English version, English is always selected and
cannot be deselected; for the Japanese version, Japanese
is mandatory.
How to programmatically set language
The developer can set or query the current runtime language
programmatically using SetLanguage and
GetLanguage.
Language changes will take effect immediately after the
SetLanguage function is executed.
If the specified language type or file is invalid, the runtime language falls back to English (for EN version) or Japanese (for JP version).
