Create Glossaries

With Glossaries, you can make sure that your terminology, product names, and other specific words are translated the way you want them. If the text to be translated contains terms from the glossary, they will be recognized and translated in the way you specified.

To create a new glossary, click Add Glossary to add a new set of terms.

Then you will see a menu in which you will be able to set a name for your glossary, choose its type (unidirectional or non-translatable), select language pairs, and the case sensitivity type.

Unidirectional vs Non-Translatable Types of Glossaries

A unidirectional glossary consists of terms in the source language and their translations into the target language.

A non-translatable glossary consists of terms that must remain unchanged in translation.

When creating a non-translatable glossary, the source language should always be selected manually, whereas the target language is set to all by default. Applying such glossaries to translation involves creating different non-translatable glossaries (for example, FR DNT, ES DNT, etc.) that will allow using these glossaries for the required language pairs in smart routing. 

Abbreviation Glossary

The Abbreviations glossary is a unique feature that focuses on abbreviations and their corresponding full forms. It is applied before sending text to Machine Translation providers to enhance the accuracy of translations. For instance:

  • Pt. → Patient

While the Abbreviations glossary type isn't available by default, it can be activated through organization-specific configurations if needed. This type of glossary is extremely beneficial when dealing with industry-specific terms, user-generated content, or informal conversations.

Your MT efforts can see significant improvements with a better understanding of abbreviations.

By implementing the glossary during the pre-processing stage, the Abbreviation Glossaries substantially minimize the chances of segment distortion.

To gain more insights on this type of glossary, please check out our blog.

Case Sensitivity 

Choose case sensitivity — this determines when terms are recognized in the source text. Let's take "Star Wars" as a sample term:

  • As Typed:
    Terms are recognized if they are exactly as in the glossary: for example, "Star Wars" will be recognized in the source text if that's how it's spelled in the glossary. 

  • Regular Case
    Terms are recognized in the source text if they are lowercase or start with a capital letter: for example, the term "star wars" will be applied as "star wars" or "Star wars".  We also support exact matching with the glossary entry spelling so "Star Wars" will be recognized and the glossary will be applied.

  • Uppercase
    Terms are recognized in the source text if they are uppercase: for the same term, "STAR WARS". "Star Wars" won't be recognized and the glossary won't be applied.

  • Lowercase
    Terms are recognized in the source text if they are lowercase, for example: "star wars". "Star Wars" and "STAR WARS" won't be recognized, and the glossary won't be applied.

Please note that you can see the examples for all cases in the table here.

Import Existing Glossary From a CSV File

To import an existing glossary from a CSV file:

  1. Upload a CSV file with all the terms in it.

    If you are using a CSV file to create a non-translatable glossary, you can import it from a file with only 1 column as well.

  2. Select Create glossary and import terms, and a new page with the glossary will open.

  3. To go back to the main page, select Glossaries in the top left.