All Collections
Lokalise Messages
HubSpot Inbox
Lokalise Messages for HubSpot: Glossary
Lokalise Messages for HubSpot: Glossary
Alex Terehov avatar
Written by Alex Terehov
Updated over a week ago

This feature is available from the Start plan and above.

Introduction

A glossary is a custom dictionary that Lokalise Messages uses to consistently translate the desired terminology according to company-wide conventions.

For Lokalise Messages, the glossary is mostly useful for the following use cases:

  • Feature names or product UI: for example, "HubSpot Service Hub" should stay untranslated.

  • Ambiguous words: for example, the word "order" could have different desired translations depending on shipping or payments contexts.

It's important to note that the glossary for Lokalise Messages would be consumed by a machine translation engine, so glossaries that the localization team maintains usually should be truncated to keep a minimum amount of terms.

Best practices

  • Include only one translation for the same source

    • For example, if you have entry like EN>DE: "Lokalise Messages">"Lokalise Messages".

    • Then there should NOT be similar entries, like these: EN>DE: "Lokalise Messages">"Nachrichten lokalisieren".

  • Glossary is case-sensitive.

    • If you need both capitalized and non-capitalized versions of a word to be included, you must include an entry for each version.

  • Terms from the glossary are applied "as is".

Uploading a glossary

On the Glossary page, you can upload a CSV files with list of terms:

After upload you can browse and manage your glossary entries:

To change Glossary entries: click on Download terms as CSV file > make adjustments in the file > click on Delete all terms > click on Choose a CSV file to upload button.

In the example above the English word "account" will always be translated as "cuenta" for Spanish language and as "рахунок" for Ukrainian.

To add glossary entries you have to upload a comma-separated values (CSV) file with the following structure:

  • The first row is a header and it must contain language codes (the order doesn't matter).

  • Subsequent rows should contain the actual glossary entries.

Please note that glossary entries are case-sensitive.

Once the entries are imported you can download them back in the same format by clicking Download CSV.

To clear your glossary, press Delete all terms.

Please note that all languages should be submitted for each term. For example, if one term has translation specified into three languages, then all other terms should be also translated in the same three languages.

Further steps

Did this answer your question?