A glossary consists of terms, their definitions and the meaning of any terminology unique to your business. It helps your translators to identify terms and apply the correct translations which speeds up the translation process and improves consistency.
Set up a Glossary
- Go to “Account” → “Glossaries”
- Create a new glossary and assign it to one or more projects
- Go to the glossary detail page by clicking on the entry and add terms by following the “Add glossary term” link
Glossary terms are used to highlight matching words or phrases in your translations. This tells your translators which terms should be translated and how.
For example your company name (e.g. “Apple”), should never be translated in any language. For this you should select the Use term for all languages option when creating a new term:
Terms that are marked as “translatable” however, (e.g. the word “Save”) can be translated in each language but in a consistent way through predefined term translations. In that case you should select Term can be translated and add translations for all desired languages:
Using the glossary during translation
When working in the translation editor, you will find matching glossary terms highlighted in the source translation and listed with additional information in the glossary tab located in the sidebar:
You can easily insert a glossary term in the target translation by clicking on the Insert button next to each listed term.
PhraseApp will also validate the presence of the terms listed in the glossary tab while typing. That way your translators can easily verify if all terms are used correctly while translating. The following states will be visualized next to each glossary term in the list by using different colors:
- not yet validated
- present in target translation
- missing in target translation
Upload terms via CSV
You can also import your glossary terms to PhraseApp via CSV. To upload a file, simply select
And then upload the file using the upload dialog:
CSV file structure
A typical CSV file for a glossary is structured like this:
term,case_sensitive,translatable,description,en-GB,de, ... "PhraseApp",true,false,"","","", ... "",true,true,"When clicking on a button save something","Save","Speichern", ...
The first line must contain the column names (“header”) and can also contain multiple locale codes. Each following row then describes an actual glossary term.
Supported columns are:
||The glossary term used as an identifier.|
||If set to
||If set to
||A description of the term, e.g. when to use it.|
The order of the columns does not matter. The file must contain only valid locale codes and must not contain any unknown columns.
A minimal file must contain at least the locale codes and may omit other columns:
en-Gb, de, fr, ... "PhraseApp","","", ... "Save","Speichern","", ...