Skip to main content

Translations

Introduction to translations​

All strings used in user interfaces, such as labels, buttons, tables, and columns, can be translated. The Thinkwise Platform provides default translations for the following languages:

  • Dutch
  • English
  • German
  • French
  • Spanish
  • Portuguese

Additional languages can be added from the Application languages screen. Thinkwise recommends to use the two- or three-letter ISO 639 language code, like en and eng, or the composite IETF language tag, like en-US, to identify a language. The Thinkwise Platform provides full support for Unicode characters, which means that any language is supported.

Application languages

Translation objects​

menu User interface > Translations

For each translatable string, a translation object is created for which a translation can be entered in the screen Translations or the tab Translation available on various other screens.

Translations screen

Generate translation objects​

Translation objects for new strings are automatically created when generating. To manually generate translation objects for new objects:

menu User interface > Translations > tab Translations

  1. Execute the task Generate translation objects generate.

An object contains, at most, the following translations, depending on the type of translation object:

  • (Single) translation
  • Translation form
  • Translation grid
  • Translation card list
  • Plural translation
  • Tooltip text - Appears when the mouse hovers over a field name, group name, tab, or column. Tooltips support many HTML tags and attributes for formatting text, but potentially harmful code like scripts are removed for security reasons.
  • Help text

Translate untranslated objects by ID​

To set the translation for the selected translation object(s) based on their identifier:

menu User interface > Translations > tab Translations

  1. Execute the task Translate using ID translate.

The enrichment task replaces underscores with spaces, removes the square brackets, and capitalizes the first letter.

note

Translate using ID is designed to generate translations in the language of the original data model, which ensures consistency within a specific language environment.

Translate untranslated objects with AI​

To generate translations for the selected translation object(s) using the translations specified in another language:

menu User interface > Translations > tab Translations

  1. Execute the task Translate using AI translate.
note

Translate using AI prioritizes translations specified for the configured fallback language. The enrichment task is only available if your branch contains two or more languages, and one must be translated. See also the enrichment Translation all untranslated objects in the table with available model enrichments.

Differences between translating objects by ID and with AI​

The following example illustrates how Translate using ID prioritizes maintaining the original language, while Translate using AI facilitates translations within your data branch.

When translating the object name "[customer_name]" from English to Dutch and the English source translation is "Customer name", Translate using ID would translate it to "Customer name". On the other hand, Translate using AI would likely translate it to "Klantnaam" since the task uses AI to identify the target language (Dutch) and translate the object name accordingly.

Delete unused translation objects​

To delete unused translation objects for the entire branch:

menu User interface > Translations > tab Translations

  1. Execute the task Delete unused translation objects delete.

Translation review​

menu User interface > Translations

The translations screen provides the option to review translations by approving or disapproving them using the Mark approved approved and Mark disapproved disapproved tasks. The prefilter Not yet approved not yet approved can be used to filter all translations that have not been reviewed yet. When disapproving a translation, feedback as to why it was disapproved is required. Disapproved translations can be filtered using the Disapproved disapproved prefilter and will also generate a validation that can be assigned.

Please note that any changes to a translation will result in the approved status being reset and the translation needing to be approved again.

note

Not every model requires a translations review. For example, single developer models, or models where translations are reviewed by an external party. Therefore, a setting named Translation review required is available in the menu Maintenance > Configuration. Uncheck this setting to hide the tasks for (dis)approving translations and the validations regarding the not yet (dis)approved translations. See also Configuration.

With link tables that are displayed as detail, it is often desirable, depending on the context, to display another translation. This is possible by including the plural translations of both master subjects, separated by a forward slash / in the plural translation of the linking table. The GUI will show the part of the translation that is not equal to that of the current master table.

For example, by giving the linked table between person and company the translation Persons/Companies, the table will have the translation Companies under person and Persons under company.

Grant access to a translator​

You can grant access to an external translator in two ways:

  • Indirect access via Excel - In the Software Factory, export the program objects for the language that needs to be translated to Excel: menu User interface > Translations > right-click > Extra > Export. Import the translations in the same way.

  • Direct access - Grant the translator direct access only to the screens Translations, Translation objects, and Help in the Software Factory. Translators are not allowed to create translation objects. You can grant access by using the default available user group and role. In IAM:

    • Create a user (menu Authorization > Users).
    • Add the user to the translation_management user group (menu Authorization > User groups > tab List > tab Users). See also Add users to a user group.
    • Assign the Translation management role to the translation_management user group (menu Authorization > Applications > tab Authorization settings > tab Authorization). See also Grant a user group access to the application.

Direct access Grant an external translator access to the Translations screen

Was this article helpful?