---
title: "Glossaries"
manual: "DeepL Translate"
version: "main"
source: "Editor/Index.rst"
rendered: "2026-10-06T20:32:38+00:00"
---

# Glossaries {#glossaries}

You can define glossaries for your translations. Each glossary has a name, a source
language and a target language. The name is made up of the page title and the target
and source languages.

![List view of glossary items](../Images/Editor/glossaries-list-view.png)

On pages with Doktype 254 (Folder) and "Use Container" set to "DeepL Glossary",
a synchronise button appears for easy synchronisation of the glossary terms listed in this page.

A glossary folder serves the pages of its own site only. Every site that should be
translated with a glossary needs a glossary folder of its own.

Possible glossary combinations in multiple language translation modes are built
on the fly, so your glossary can be used from any target to source, **except** the
default system language.

Each glossary shows you the current sync status to the DeepL API in the page settings.

![Page settings tab \*DeepL Translate\* with not synced glossary](../Images/Editor/glossary-sync-tab-not-synced.png)

Adding terms is done through the list module. A term may be up to 1024 characters
long. DeepL counts this limit in bytes, not characters, so a term containing
umlauts, CJK characters or emoji reaches the limit earlier than 1024 characters.
An umlaut takes two bytes, a CJK character three and an emoji four. Saving a
term that exceeds 1024 UTF-8 bytes is rejected with an error message: a new
entry is not created, an existing entry keeps its previous term.

![Add entry via add record](../Images/Editor/glossary-add-term.png)

To generate a glossary translation, simply translate the page into the required
glossary language using the TYPO3 translation dropdown. A custom translation dropdown
will be displayed, which will only accept languages in which glossary entries can be created.

![Custom translation dropdown in list view](../Images/Editor/glossary-page-translation.png)

![Possible translations based on source language EN](../Images/Editor/glossary-page-translation-select.png)

> [!NOTE]
> DeepL glossaries only know base language codes. Site languages sharing a
> code, like English (UK) and English (US), feed one common glossary, and
> only one of them provides its terms. The site configuration decides which
> one, see [Site configuration](../Administration/SiteConfiguration/Index.html#site-configuration).

After that you can make translations with the *Translate to* button.
As the glossary entries are made for not using DeepL standard wording, the
ability of translating entries by DeepL is disabled.

![Backend list view of glossary entries, original language english, translated to German](../Images/Editor/glossary-entry-list.png)

You can retrieve the current sync information of this glossary to the API in the
page settings, tab **DeepL Translate**.

> [!NOTE]
> Current **NO** Automatic sync is performed on save. Save and trigger sync manually.
>
> Every change of the terms of a folder marks its glossaries as out of sync:
> adding, editing, hiding, deleting, translating, moving or copying a term.
> A glossary out of sync is not used for translations until the folder is
> synchronized again.

In each glossary directory, a button is enabled to synchronise that glossary.

After sync the tab *DeepL Translate* should look like this:

![Tab "DeepL Translate" with set ID, time of last sync and ready status](../Images/Editor/glossary-sync-tab-synced.png)