---
title: "Site configuration"
manual: "DeepL Translate"
version: "main"
source: "Administration/SiteConfiguration/Index.rst"
rendered: "2026-10-06T20:32:38+00:00"
---

# Site configuration {#site-configuration}

DeepL glossaries only know base language codes like `en`, `pt` or `de`,
see the [DeepL glossary documentation](https://developers.deepl.com/api-reference/multilingual-glossaries).
A glossary with the target language `EN` is used for translations into
`EN-GB` and `EN-US` alike, the same applies to `PT-PT` and `PT-BR`.

The glossary language code of a site language is taken from its
**Locale**. When several site languages share a code, for example
English (UK) with `en_GB` and English (US) with `en_US`, only one of
them can provide the terms of that glossary.

## Glossary terms {#site-configuration-glossary-terms}

The field is shown in the **DeepL Settings** of each site language
except the default language in the **Site Management > Sites**
module, below the DeepL target language.

-   **deeplGlossaryTerms**

    -   *Type:* string
    -   *Default:* automatic

    -   **`automatic`**

        The site language provides the glossary terms of its language code
        according to the rules below.

    -   **`preferred`**

        The site language provides the glossary terms of its language code,
        even when another site language sharing the code has terms too.

    **config/sites/\<identifier>/config.yaml**

    ```yaml
    languages:
      -
        languageId: 1
        title: 'English (UK)'
        locale: en_GB.UTF-8
        deeplTargetLanguage: EN-GB
      -
        languageId: 2
        title: 'English (US)'
        locale: en_US.UTF-8
        deeplTargetLanguage: EN-US
        deeplGlossaryTerms: preferred
    ```

## Which site language provides the terms {#site-configuration-glossary-terms-rules}

The synchronization decides per glossary language code:

1.  The default language always provides the terms of its own code. A
    site language sharing that code is never used, even when it is marked
    as `preferred`.
1.  Otherwise the site language marked as `preferred` is used. When
    several are marked, the one with the lowest language id wins.
1.  Otherwise the site language with the lowest language id having at least
    one glossary term is used.

Terms are never mixed between site languages. A term missing in the
selected site language is missing in the glossary, it is not taken from
another site language sharing the code.

Example: a site with the default language German and the site languages
English (UK) and English (US) builds one `de` to `en` glossary. Marking
English (US) as `preferred` makes it use the terms of English (US), the
terms of English (UK) are ignored.

## Warnings during the synchronization {#site-configuration-glossary-terms-warnings}

The synchronization warns when the site configuration does not decide
unambiguously:

-   several site languages sharing a code have terms and none of them is
    marked as `preferred`,
-   several site languages sharing a code are marked as `preferred`,
-   a site language sharing the code of the default language is marked as
    `preferred`.

The warning is shown as a message after using the synchronize button in the
backend, printed by the [deepl:glossary:sync](../../Housekeeping/Index.html#sync-cli) command and
written to the TYPO3 log. Mark exactly one site language per shared code as
`preferred` to resolve it.