Multilingual support

This release introduces a new mechanism for handling multilingual resources in the following runtime modules:

  • PowerBuilder runtime files

  • Cloud App Launcher

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

Detailed documentations are provided in PowerBuilder's What's New.

How to support multilingual resources in Cloud App Launcher

The Cloud App Launcher now supports multilingual resources.

  • (Installer & Runtime) The launcher automatically uses the client's Windows Display Language for both installation and runtime resources. If the client's Windows display language is not supported, the launcher falls back to English (for EN version) or Japanese (for JP version).

    • Each supported language is stored in a dedicated .lng file (e.g., english.lng, french.lng, japanese.lng). They will be automatically packaged into the launcher installer.

    • To use the user-defined language file, name the file as custom.lng and place it in the runtime language folder, for example, C:\Program Files (x86)\Appeon\Common\PowerBuilder\Runtime 25.1.0.6180\lang. By default, a custom.lng file is already provided in this location and initially contains the same content as english.lng.

    • Only one custom language file is allowed.

    • The file content format is TextID, TextDescription. Edit only the text descriptions.

    • You can only change the custom.lng file. Changes made to any other .lng file (e.g., english.lng, french.lng, japanese.lng) will not take effect.

  • (Installer & Runtime) Developers can specify a language when packaging the launcher, ensuring that both the launcher installer and runtime resources run in the chosen language. (①)

    When Use Windows Language is selected, the Windows Display Language configured for the current user on the client will be used.

  • (Runtime only) Developers can also choose to allow the user to change the language for the launcher runtime resources during the launcher installation process. (②)

    The end user will be offered with the language option (similar to ①) when installing launcher.