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

Any user of the project 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.

If it is required 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. By default, the glossary is private only to this project. Use the shared glossary from another project to use it in the editor or modify it. You can modify the shared glossary in any project. The changes will immediately take an effect on all projects in the team.

This feature "Shared glossary" is available starting from the Pro plan. 

You can separate terms with a comma to define word forms, for example "account,accounts,accounted".

You can upload CSV file with glossary. The CSV file rules are:

  • Separated with ; (semicolon)
  • Contain header row
  • First column is "term"
  • Second column is "description"
  • Each next two columns header must be language ISO code as defined in your project (e.g. "ru"). First of each of two columns itself should contain term definition in respective language and the second column of the pair should contain term description in the language.

If there is a description specified in target language it would be shown in the inline dropdown instead of general description.

Example .csv file:

term;description;en;en;ru;ru;lv_LV;lv_LV

first,thefirst;This is a sample term;first sample;This is the description of glossary sample;Сэмпл;;Piemērs 1;Apraksts piemēram 1

second;Second sample term;second sample;;Сэмпл;Образец описания по-русски;Piemērs 2;Apraksts piemēram 2
Did this answer your question?