This feature is available starting from the Essential plan and above.

Use a glossary (your project term base) to keep project translations consistent.

Any contributor can define the terms for the project. Each term is defined and described in the glossary. If a term is used in the source language translation, it will automatically show up in the editor's inline suggestion box.

Index

Setting up glossary

To get started, open your project and proceed to the Glossary page by clicking the corresponding icon.

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

On the General tab you can provide the following data:

  • Term — the term that you would like to add to your glossary.

  • General description — optional explanation of your term that will be visible to the translators. This description will be shown if a translated description is not provided for a given language (see below).

  • Non-translatable — whether the term should be translatable. Some acronyms like "PNG" or "HTML" are non-translatable whereas terms like "browser" or "site" have to be translated.

  • Case-sensitive — whether your term is case-sensitive. For example, acronyms like PNG or BMP can be marked as case-sensitive.

  • Tags — add up to three tags to your glossary entry. You can choose existing tags or create the new ones.

Proceed to the Translations and descriptions tab. Here you can translate your term into the project languages and (optionally) provide translated descriptions. If the translated description is not available for a language, a general description will be used instead. Not that this tab will not be accessible if you've set Translatable option to Off. Note that it is not mandatory to translate the added term before adding it to the glossary.

Extract terms

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, press the Extract terms button. You have to set up the minimum length of the words and the minimum amount of times the word appears in the project to extract a word as a term.

Managing glossary entries

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

Here you can see:

  • The actual term ("callback function").

  • Its general description ("A special function to run when a given operation was finished").

  • What languages this term was translated into (Russian, French, Arabic, Dutch, Catalan).

  • Tags ("technical").

  • Who has added this term and when ("May 13, 2019; added by Joe).

  • Also you can delete the term or find all the keys containing this term in the current project.

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

Downloading and uploading terms in CSV format

You may export all glossary entries and their translation to your PC in CSV format by pressing the Download CSV button on the Glossary page.

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

When preparing a CSV file, please follow these rules:

  • Semicolons ; should be used as separators.

  • The file has to contain a header row.

  • The first column in your file should be term.

  • The second column is description.

  • The third column is casesensitive which can be either true or false (or yes / no).

  • The fourth column is translatable which can be either true or false (or yes / no).

  • Each of the next two column headers must be the language ISO code as defined in your project (e.g. ru or de_DE). The first of the two columns should contain a term definition in the respective language and the second column of the pair should contain a term description.

Here is an example of a valid .csv file:

Finally, note that you can separate terms with a comma to define word forms, for example "account,accounts,accounted".

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 Arabic language. In this case French translation will be updated in your glossary, whereas Arabic translation and description will be left intact.

Using glossary entries

Every detected term will be shown in the translation editor:

It shows translation and description for the currently selected language. 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.

Key tags and glossary entries

Glossary entries are displayed for the key tags as well. Suppose you have a translation key with the "api" tag:

You create a new glossary entry:

Then you proceed to translating the "export" 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.

Shared glossary

The Shared glossary feature is available from the Pro plan and above.

You can share the glossary to make it available for other projects within the team. You can set up the glossary options in the Project settings

There are three available options:

  • The glossary is private and cannot be used in any other projects (this is the default option). Note that a single project can have only one glossary.

  • The glossary is shared and can be used in other projects.

  • The current project should use a shared glossary from another project.

So, one of your projects should have The glossary is shared option enabled. Other projects can then use this shared glossary.

The shared glossary can be modified in any project. The changes will immediately take an effect on all other projects in the team that utilize the same glossary.

Glossary permissions

Role

Glossary type

Accessed from

Create term

Read terms

Contributor

Regular

N/A

yes

yes

Manager

Regular

N/A

yes

yes

Contributor

Shared

Original project

yes

yes

Manager

Shared

Original project

yes

yes

Contributor

Shared

Linked project

yes

yes

Manager

Shared

Linked project

yes

yes

Role

Glossary type

Accessed from

Update term

Delete term

CSV download

Contributor

Regular

N/A

yes

no

yes

Manager

Regular

N/A

yes

yes

yes

Contributor

Shared

Original project

yes

no

yes

Manager

Shared

Original project

yes

yes

yes

Contributor

Shared

Linked project

yes

no

yes

Manager

Shared

Linked project

yes

no

yes

Role

Glossary type

Accessed from

Delete all terms

Extract terms

CSV upload

Contributor

Regular

N/A

no

no

no

Manager

Regular

N/A

yes

yes

yes

Contributor

Shared

Original project

no

no

no

Manager

Shared

Original project

yes

yes

yes

Contributor

Shared

Linked project

no

no

no

Manager

Shared

Linked project

no

no

no

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

Did this answer your question?