Skip to main content

Multilanguage

Multilingual behavior​

General​

Multilingualism is in principle based on the language used in the request, or the user language. Specifically, means:

  • Request all reading actions of a user, such as a template or dataset
    • are executed in the user language
    • the user receives the requested page in his own language
  • All write actions of a user, such as performing an activity
    • are executed in the user language
    • the activities use the same language as the reading actions
    • ⚠️the result of write actions depends (on the language) of the user
  • All poller tasks, such as Timed, Deadline and Taskqueue events, do not have a user...
    • ⚠️are run on the platform language.
  • If a user does not have/provide a language, the platform language is used.
  • The platform language
    • has limited value
    • a user who does not understand the platform language does not feel any limitations
    • This can be changed later with minimal hassle

Setting values​

When values are filled, for example with a Mapping of type Assign (=), or in the form logic with a Set Value, then the behavior is as follows:

With Multi language -> multi language all existing translations are overwritten, even if the new value is missing a language .

  • Old value: {nl: Rozen, en: Rose}
  • Mapped value: {nl: Tulp, de: Tulpe}
  • Then the result becomes: {nl: Tulp, de: Tulpe} (and therefore no mix: {nl: Tulp, en: Rose, de: Tulpe})

With Multi language -> single language, the user's language is used. If that translation is missing, the platform language. If that translation is also missing, a random translation that is available will be used.

At Single language -> multi language, the user's language is filled. If the user has no language, will be filled in for the platform language. All other languages are cleared.

Conditions​

Two multi-language values are equal if all translations are equal. For example

  • {nl: Rozen, en: Rose} is equal to {nl: ROZEN, en: ROSE} (since we are case insensitive)
  • {nl: Rozen, en: Rose} is not equal to {nl: Rozen} or {nl: Rose}

A single language value is equal to a multi language value, if the multilanguage value converted to a single language value is the same. So

  • {nl: Rozen, en: Rose} is equal to Rozen for a Dutch user
  • {nl: Rozen, en: Rose} is not equal to Roses for an English user
  • {nl: Rozen, en: Rose} is equal to Rozen if the platform language is Dutch and the user has no language
  • {nl: Rozen, en: Rose} is equal to Rozen if the platform language is Dutch and the user is German

Mandatory​

A mandatory multi-language field must have at least one of the languages filled. It doesn't matter which language it is filled with .

To empty​

When a multi language field is cleared, for example in the form logic with Set Empty, all languages are cleared.

Missing translations​

If a language is missing, another language will be shown.

However, at this time we make no guarantees as to what other language will be displayed. If you want to avoid encountering an unexpected language, it is necessary to either not translate an attribute or to translate it into all languages. There are several choices for an alternative language, and we postpone the behavioral choice.

  • An alternative dialect, for example American English en-US instead of British English en-GB, or en-US instead of of en.
  • An alternative language based on the platform language.
  • An alternative language based on the user's preferences, the user can indicate which language or languages in order he prefers.

Single language attributes make multi language​

It is possible to convert a single language attribute, which is a single value of type string, to multi language. Existing values are retained, these existing values are the platform language for this.

⚠️On the contrary, when converting a multi language attribute to single language, the entered value may be lost. Even if the platform language is filled, the value can be lost. If a value is set to a single language attribute, and that value is subsequently not changed, not even internally by system tasks. Then when the attribute is first made multilanguage and then made single language again, will retain its value of .

Translations from the studio​

Translations from the studio via Crowdin​

Crowdin https://crowdin.com/ is an application that helps you translate texts. It provides support in the form of suggestions based on automatic translations (such as google translate) and previous translations. Furthermore, Crowdin includes a rating and branching system. Crowdin further checks the basic syntax, as whether the placeholders are returned and the punctuation and capitalization match. For a smooth translation, we provide some context in addition to the original language. We provide the name of the attribute, the case reference and the caseid and casetype.

It requires some settings to be set on my grexx. An access token, which can be generated https://crowdin.com/settings#api-key with Source files & strings and Translations be set to Read and Write, and a project id via https://crowdin.com/project/<PROJECT-NAME>/tools/api.

Templates​

Multi language templates can be created using the template part. This can be created by selecting a piece of text and using the keyboard shortcut CTRL-L (MAC CMD-L). Alternatively, lang. can be typed. Here must be entered a piece of plain text, where additional placeholders can be using curly brackets, for example My name is {{ name }} and my hobbies are {{ hobbies }}, do you also like {{ hobbies }}?, where name and hobbies is a freely fillable template. The order of the placeholders not have to remain the same for the translation. The Grexx Platform does not distinguish between starting and ending whitespaces, so {{name}} and {{ name }} are considered the same, but crowdin does not recognize that these are the same and will give warnings that a placeholder is missing.

To get the literal text My name is {{ name }} including curly braces, it is necessary to leave the placeholder name empty.

Technically, a multilanguage template is identified by a unique ID, which is automatically generated. As result, a copied multilanguage template part must be retranslated to ensure its unique ID is different.

Reference​

The reference of a case cannot be translated. This is because a reference is a cached field.

Casedata​

Support​

The casedata cannot currently be translated, but we are working to make this possible.

How to set​

Multilanguage casedata requires 2 things

  • per platform indicates that it contains multilanguage casedata and which languages are supported
  • Single value string attributes can be set to be multilanguage.