While glossaries used at training stage are conceived as more general, run-time glossaries should contain more specific terminology, for instance depending on the purpose of a project or on a specific client's requirements. As they are applied as search-and-replace tools, there are two requirements that run-time glossaries have to meet when created:
- Glossary entry uniqueness - all source terms should be unique and include the same translation. This means that if a term (e.g., 'football') is already entered in the glossary with a translation (e.g., 'fútbol'), no other entries should be included in the same glossary for the same source term, especially if the translation is then different (e.g., 'balón').
- Term precedence - longer terms should always come before shorter terms. If a shorter term is also included in a longer term (e.g., 'table' vs 'kitchen table'), the glossary will only apply to the shorter term if this comes before the longer one in the list. On the contrary, if the longer term comes before the shorter one, the glossary will apply to both cases.
|Note:||KantanMT supports run-time glossaries in two formats: TBX and XLSX (it must be called glossary.xlsx).|
If you encounter any problem or need help, please contact us at email@example.com.