Translations

Simple Translations

You can translate various default screen elements into other languages using a simple JSON array placed in the translations event of the app configuration.

For example:

{
    "Save": "Speichern",
    "Cancel": "Abbrechen"
}

This setup would modify all "Save" and "Cancel" buttons across the user interface to reflect the translations provided.

Dynamic Translations

You can dynamically set translations by using conditional statements in the before-process code event.

For instance, if your links include a URL parameter for language preference, you can adjust the translations accordingly:

if (url_parameters.lang == "de") {
    translations = {"Save":"Speichern", "Cancel":"Abbrechen"};
}
if (url_parameters.lang == "es") {
    translations = {"Save":"Ahorrar", "Cancel":"Cancelar"};
}

To revert translations to the default settings, assign a non-valid object to the translations variable, such as:

if (url_parameters.lang == "en") {
    translations = "reset";
}

Screen Specific translations

If you aim to apply translations to specific screens only, you must utilize if statements within the app-wide before-process event to correctly identify and target the desired screen.

It's crucial to understand that translations added in a screen-specific before-process event will apply to all screens, not just the intended one. For true screen-specific translations, you should implement them in the app-wide before-process event. Use if conditions to apply translations selectively based on the screen context, and include a reset condition for other screens to avoid unintended changes.

For example, if you wish to translate the "Save" and "Cancel" buttons exclusively for screen_2, you can use the following approach:

if (current_context == "screen_8") {
    translations = {"Save":"Speichern", "Cancel":"Abbrechen"};
} else {
    translations = "reset";
}

Remember to include an else clause or an additional if condition to revert the translations to their defaults. Failing to reset the translations will result in them being applied to all screens, not just the intended ones.

Limitations

• The default translation variables are only effective for certain interface keywords.
• It does not cover user-generated content, including headers, footers, or text on screens.
• Direct translations of data from Podio, such as help text or category values, are not supported.