> For the complete documentation index, see [llms.txt](https://docs.eximee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/tworzenie-formularza/tlumaczenia.md).

# Translations

## “Translations” tab

Tab **Translations**, available in the application editor, enables adding translations for the application, composite components, and business components. Here you can also add keys that override the application's default content (details in the chapter *Platform translation keys*).

This tab also allows adding or modifying validator messages associated with components (details in the chapters [*Composite validations*](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/praca-z-komponentami-bazowymi/walidacja-wartosci-komponentow/walidacje-zlozone-wlasne.md) and [*Script validators*](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/logika-biznesowa/scriptcode/walidatory-skryptowe-validationscript.md)).

<figure><img src="https://2112972046-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CssJT0zIo4SJQLbSZ6l%2Fuploads%2FNdm8xCvfuhiggW20oCUy%2Fimage.png?alt=media&amp;token=9697e757-f2e2-4bee-bd43-c374e2f98af2" alt=""><figcaption><p><em><strong>Figure 1.</strong> Application editor window - “Translations” tab</em></p></figcaption></figure>

***

### Editing the key and value

After selecting a cell in the table, you can edit both the key and the translation values for individual languages.

For multiline values, the edit field will automatically expand to show the entire content.

<figure><img src="https://2112972046-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CssJT0zIo4SJQLbSZ6l%2Fuploads%2F0KSQa7Edp3Dlqrb2mwOu%2Fimage.png?alt=media&amp;token=74a29447-462d-47b1-b220-e5dd1ff03558" alt=""><figcaption><p><em><strong>Figure 2.</strong> Editing translations</em></p></figcaption></figure>

***

### Deleting a key

To delete an entire translation row, click the icon on the right side of the given key.

<figure><img src="https://2112972046-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CssJT0zIo4SJQLbSZ6l%2Fuploads%2FNa0PUIfbh1n6tBEzRtwk%2Fimage.png?alt=media&amp;token=198703e0-a24b-4c12-9303-e534bca6a51e" alt=""><figcaption><p><em><strong>Figure 3.</strong> Deleting a translation key</em></p></figcaption></figure>

After deleting a key, a notification will appear at the bottom of the screen with the option to undo the action.

<figure><img src="https://2112972046-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CssJT0zIo4SJQLbSZ6l%2Fuploads%2FOJw6hfM36Bp5OT84xSZm%2Fimage.png?alt=media&amp;token=5f3df8f4-be13-4100-9960-d29c30f619f1" alt=""><figcaption><p><em><strong>Figure 4.</strong> Notification with option to undo key deletion</em></p></figcaption></figure>

The keys of a deleted application element (component, page, step, validator, service, or component item) are automatically removed by Eximee Designer together with the element. The rules are described in the chapter [Deleting keys together with an application element](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/tworzenie-formularza/tlumaczenia/usuwanie-kluczy-razem-z-elementem-wniosku.md).

***

### Adding a key

It is possible to add a translation for every application element displaying text — titles, descriptions, labels, validation messages, and content returned by external services.

Keys corresponding to validation error messages are added automatically when a validator is added. The exception is **script validators**, for which the key must be added manually.

To add a new key, use the button **Add key** located above the language columns.4

<figure><img src="https://2112972046-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CssJT0zIo4SJQLbSZ6l%2Fuploads%2FOuMGJBWjpO2hF1HSqfcq%2Fimage.png?alt=media&amp;token=cdcb9610-f4bc-4a5e-978c-9f5b5b9133a5" alt=""><figcaption><p><em><strong>Figure 5.</strong> Button used to add a new translation key</em></p></figcaption></figure>

Clicking adds an empty row, in which you must fill in at least the key name (column *KEY*).\
If the field remains empty, the system will automatically assign the name:

* `empty`
* `empty.copy`
* `empty.copy1`\
  and subsequent ones, if needed.

<figure><img src="https://2112972046-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CssJT0zIo4SJQLbSZ6l%2Fuploads%2FjF7prxyi2PIYUR5GglvD%2Fimage.png?alt=media&amp;token=515153e0-810c-4d82-bd84-af8fb1e1013f" alt=""><figcaption><p><em><strong>Figure 6.</strong> Row after adding a key and not filling in its name</em></p></figcaption></figure>

***

### Selecting the default language (tag)

The default language can be selected in the table header. This option is available only while editing the process.

The default language is **Polish**.

To set a language as default, click the star icon next to the language code. ![](https://2112972046-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CssJT0zIo4SJQLbSZ6l%2Fuploads%2FPeA75FbrHMy8Za2Bxbqt%2Fimage.png?alt=media\&token=29098ee9-35e1-4f73-855f-8eb9ab80b267)\
A yellow star indicates the currently selected default language. ![](https://2112972046-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CssJT0zIo4SJQLbSZ6l%2Fuploads%2FLnTJADB9yogrt9rxIiV5%2Fimage.png?alt=media\&token=0c739e23-83b7-465c-83fe-e23eaadaf96d)

<figure><img src="https://2112972046-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CssJT0zIo4SJQLbSZ6l%2Fuploads%2Fw7E7cye4xOmSvp8WshjF%2Fimage.png?alt=media&amp;token=55cc9402-b0c0-4ce2-b40f-569058524eac" alt=""><figcaption><p><em><strong>Figure 7.</strong> Selecting the translation language</em></p></figcaption></figure>

***

### Filtering empty translations

To hide keys without translations, click the icon in the column **KEY**.

The active filter is indicated by a crossed-out “eye” symbol ![](https://2112972046-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CssJT0zIo4SJQLbSZ6l%2Fuploads%2F2175b1xxVkCWXKPxx2me%2Fimage.png?alt=media\&token=5778fb83-3b9f-4372-816f-dd81e3cb7343). Additionally, information is displayed about the number of hidden keys ![](https://2112972046-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CssJT0zIo4SJQLbSZ6l%2Fuploads%2FH0hDfAH1qauorQTTw1zZ%2Fimage.png?alt=media\&token=55d91baf-08e9-4d10-bbfe-c81c2dd3b7dc).

***

### Searching translations

The search works for both key names and translation values.

<figure><img src="https://2112972046-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CssJT0zIo4SJQLbSZ6l%2Fuploads%2FoL5QE8xcOpYRujhLLhZM%2Fimage.png?alt=media&amp;token=3ebbda3d-f569-4d25-93be-803bc93412f9" alt=""><figcaption><p><em><strong>Figure 8.</strong> Searching translations</em></p></figcaption></figure>

If no results are found, the following message is displayed:

```
We did not find a key or translation: ${szukanyTekst}
```

At this point, the user is also offered the option to add a new key.\
After the key is added, the search field is automatically cleared.

***

### Adding and editing languages

To add a new language, click the add new column button on the right side of the table.

<figure><img src="https://2112972046-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2CssJT0zIo4SJQLbSZ6l%2Fuploads%2FWRR1BjGwhIVGxGqptcVw%2Fimage.png?alt=media&amp;token=6cc9143b-2915-4628-997f-03ed3de2b32c" alt=""><figcaption><p><em><strong>Figure 9.</strong> Button for adding a new translation language</em></p></figcaption></figure>

The language name (tag) can be changed by clicking its header.

**Language code** should comply with the standard **ISO 639**, written in lowercase.\
The list of supported codes is available at:\
<https://www.oracle.com/technetwork/java/javase/java8locales-2095355.html>

***

## Determining the language used when opening the application

When the application is opened for completion, the system determines the language in the following order:

#### 1. The “locale” parameter in the URL

If the input address contains the parameter `locale`, and the template contains translations for the specified language, then that language will be used.

**Example:**

```
https://url.eximee/webforms/ek/index.html?locale=en
```

***

#### 2. Accepted browser languages (Accept-Language)

If the URL parameter is not available, and in the Webforms configuration the parameter:

```
server/locale/browserLocaleAllowed = true
```

the system will take the language from the header `Accept-Language`, provided that the template has the appropriate translations.

**Example:**

```
https://url.eximee/webforms/ek/index.html
Accept-Language: pl-PL,pl;q=0.9,en-US;q=0.8,en;q=0.7,en-gb;q=0.6,fr-FR;q=0.4,fr;q=0.3,es-CO;q=0.2,es;q=0.1
```

***

#### 3. Default template language

If none of the above conditions are met, the **default template language**, set in Eximee Designer.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/tworzenie-formularza/tlumaczenia.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
