# Translations ## "Translations" tab Tab **Translations**, available in the application editor, allows adding translations for the application, composite components, and business components. In this place, you can also add keys that override the default application content (details in the chapter *Platform translation keys*). This tab also allows you to add or modify validator messages associated with components (details in the chapters [*Composite validations*](/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/praca-z-komponentami-bazowymi/walidacja-wartosci-komponentow/walidacje-zlozone-wlasne.md) and [*Script validators*](/documentation/documentation-en/budowanie-aplikacji/logika-biznesowa/scriptcode/walidatory-skryptowe-validationscript.md)).

Figure 1. Application editor window - "Translations" tab

*** ### Editing a key and values 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 2. Editing translations

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

Figure 3. Deleting a translation key

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

Figure 4. Notification with an option to undo key deletion

*** ### 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 after adding a validator. 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 5. Button used to add a new translation key

Clicking adds an empty row in which at least the key name must be filled in (column *KEY*).\ If the field is left empty, the system will automatically assign the name: * `empty` * `empty.copy` * `empty.copy1`\ and subsequent ones, if needed.

Figure 6. Row after adding a key and not filling in its name

*** ### 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. ![](/files/bfbdce0d497da4e150d142e0a35be453a829deac)\ The yellow star indicates the currently selected default language. ![](/files/71f5d613de9bdb6171a90997cda23435f870aaed)

Figure 7. Selecting the translation language

*** ### Filtering empty translations To hide keys without translations, click the icon in the column **KEY**. The active filter is marked with a crossed-out eye symbol ![](/files/91d5cbbdf33ed50da9209bc224e00b17dfe78198). In addition, information about the number of hidden keys is displayed ![](/files/90fa31b1947fd59182585baaf80dc25697343480). *** ### Searching translations The search works both by key names and by translation values.

Figure 8. Searching translations

If no results are found, the following message is displayed: ``` We could not find a key or translation: ${szukanyTekst} ``` At this point, the user also receives a suggestion to add a new key.\ After adding the key, the search field is automatically cleared. *** ### Adding and editing languages To add a new language, click the add new column button located on the right side of the table.

Figure 9. Button for adding a new translation language

The language name (tag) can be changed by clicking its header. **Language code** should comply with the **ISO 639**standard, written in lowercase.\ The list of supported codes is available at:\ *** ## Determining the language used when opening an application When taking an application to fill in, the system determines the language in the following order: #### 1. The "locale" parameter in the URL If the input address contains the `locale`parameter and the template contains translations for the given language, that language will be used. **Example:** ``` https://url.eximee/webforms/ek/index.html?locale=en ``` *** #### 2. Browser accepted languages (Accept-Language) If the URL parameter is not available and in the Webforms configuration the parameter: ``` server/locale/browserLocaleAllowed = true ``` then the system will read 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 is used. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/interfejs-uzytkownika/formularze/tworzenie-formularza/tlumaczenia.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.