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 the way you specified.
Create a new glossary
Click on "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, non-translatable, or abbreviation), upload the file with terms, and select the case sensitivity type:
What is the difference between unidirectional and 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 takes 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.
Сonsists of abbreviations and their expansions that happen before sending the text to MT providers to increase the precision of the machine translation. For example:
Pt. → Patient
Whether you’re working with industry-specific terminology, user-generated content, or informal conversations, the chances are that your MT efforts can benefit from a better understanding of ad hoc abbreviations. By applying the glossary before in the pre-processing phase, Intento Abbreviation Glossaries dramatically cut down the risk of segment distortion. Read more about this type of glossary in our blog.
Choose case sensitivity — this determines when terms are recognized in the source text. Let's take "Star Wars" as a sample term.
Regular: 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.
Upper: 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.
Regular and upper: includes all cases described above. Terms are recognized if they are lowercase, uppercase or start with a capital letter: for example, "star wars", "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.
As is: 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.
Please note that you can see the examples for all cases in the table here.
How to import an existing glossary from a .csv file
Upload a .csv file with all the terms in it. Please note that it should have the following structure:
NB: 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.
Select Create glossary and import terms. A new page with the glossary will open. To go back to the main page, select Glossaries in the top left.