Glossaries and Translations
Learn how to manage glossaries when your content is going to be translated. You can have a glossary in multiple languages, but you need to reference the terms by their xml:id.
Glossaries, like any other topic, can be in multiple languages. You add each required language to the topic, and then the topic can contain the content for the source language and the translations for each additional language (see Working in Translation View).
For a glossary in multiple languages, you need:
-
A "glossary" topic to contain the glossary term definitions.
This topic will be translated into different languages, so you have a single glossary topic with versions in English, French, German, Spanish, etc. To find out more, see Create a Glossary Topic.
-
Regular topics that contain text that references your "glossary" topic.
These topics will also be translated into different languages. For the glossary references, Paligo will look in the version of the glossary that matches the language of the topic. For example, if the French version of a regular topic references "vanne", Paligo will look for "vanne" in the French version of the glossary topic.
Most types of glossary reference will work in all languages (see Glossary References), but there is one exception. If you want a term in your text to refer to a glossary entry, but the text does not
match the glossary term, you will need to use an xml:id reference. To find out more, see Topic Term is Different to Glossary
Term.
When your content is translated, it is important that only the text is translated. Do not translate element names, attribute names, or attribute values.