Use a glossary to keep project translations consistent. Any contributor can add terms to the project glossary. If a term is used in the source language translation, it will automatically show up in the editor's inline suggestion box.

To get started, open your project and proceed to the Glossary page by clicking the corresponding menu item:

You'll see an invitation to add new entries:

If your glossary already contains some terms, you'll see a different screen:

Here you can filter, sort, and search your entries as well as add new entries and perform other actions.

Let's start by adding a new entry.

Press the Add term button to add a new entry to the glossary:

On the General tab you can provide the following data:

Next, proceed to the Translations and descriptions tab:

Here you can translate your term into the project languages and (optionally) provide translated descriptions. Translation descriptions will be displayed alongside general term (or source language) description for the matching terms. Note that the Translations and descriptions tab will not be accessible if you've set the Translatable option to Off.

Please note that it is not mandatory to provide translations for the term before adding it to the glossary.

Keeping translations consistent across the whole project is always important. Using the Extract terms feature allows you to automatically extract the terms repeated a certain number of times and add them to the glossary.

To get started, click More > Extract terms on the Glossary page:

You'll be presented with the following dialog:

Once you are ready, click Extract. All found words will be added to the glossary as regular terms.

After a new term is added, it will appear on the Glossary page.

Here you can see:

You can switch between the grid and the list view using these controls in the top menu:

Use the search bar to find a specific term (you can enable or disable case sensitive search):

Filter and sort your glossary entries using the corresponding dropdowns:

Finally, you can delete all glossary entries by clicking More > Delete all:

You can export all glossary entries and their translation to your PC in CSV format by clicking More > Download CSV button on the Glossary page:

The terms can also be imported to the glossary from the CSV file by clicking More > Upload CSV button.

When preparing a CSV file to upload, please follow the following rules:

Here is an example of a valid .csv file:

When you are uploading a CSV file with glossary entries, all existing entries with the same terms will be updated. However, if the one or more languages are skipped in your CSV file, then the corresponding translations and descriptions will be left intact.

For example, suppose you have a glossary term "router" with translations and descriptions in French and Arabic. Next, you upload a CSV file with the updated French translation for the term "router". However, your file does not provide any data for the Arabic language. In this case French translation will be updated in your glossary, whereas Arabic translation and description will be left intact.

Every detected term will be shown in the translation editor:

You'll see the actual term, its general description in the base language (English in the example above), its translation, and its description in the target language (if present). Also you can see who added this term and when, as well as the tag attached to this entry (some entries may have no tags).

Click on the term to add it to the translation editor box.

We use stemming to automatically match glossary terms to different word forms. Stemming is the process of reducing a word to its stem that affixes to suffixes and prefixes or to the roots of words known as "lemmas".

This means that we will match similar forms of words based on their root form.

Example: If you have a term Change in your Glossary, we will automatically match it to the following words in the text: change, changing, changes, changed, changer.

Stemming is supported only in the following languages: Catalan, Danish, Dutch, English, Finnish, French, German, Italian, Norwegian, Portuguese, Romanian, Russian, Spanish, Swedish for now.

When creating a glossary term, you can also manually separate terms with a comma to define word forms, e.g. "account,accounts,accounted". In this case automatic stemming will not be applied and we will match text to one of the forms that is manually provided in the glossary term.

Terms added to the glossary are exempt from built-in spelling and grammar checks. Below are a couple of real-life examples.

Case 1

Outcome: Translation is not highlighted with spell-checker.

Case 2

Outcome: Translation is not highlighted with spell-checker.

Case 3

Outcome: Translation is still highlighted until it’s hovered over.

Glossary entries are displayed for the key tags as well. Suppose you have a translation key with the "API" tag. Then you create a new glossary entry:

Then you start translating the key with the "API" tag:

The glossary entry is displayed for the assigned tag! Note that this glossary suggestion has a special "label" icon meaning that it is related to the tag, not to the actual key value.

Also please note that the tags are case-sensitive. In other words, if your tag is named "api", the "API" glossary entry won't be displayed.

You can share the glossary to make it available for other projects within the team. To setup glossary options, proceed to More > Settings:

There are three available options:

The shared glossary can be modified in any project: specifically, you can edit the existing terms and add new ones. The changes will immediately take effect on all other projects in the team that utilize the same glossary. Please note that certain actions can only be performed in the original glossary: for instance, terms deletion.

Manager role means a project admin with the "Manage glossary" permission set on the project level.