Preferred terms, forbidden terms, do-not-translate. LINA and reviewers see the same list.
Language you can ship.
Define which terms to use, avoid, or leave untranslated across every language.
LINA checks the glossary before drafting, so approved product terms carry into new translations.
Use the same terminology across your product, support content, and marketing.
One inconsistent product name can become ten inconsistent translations. Keep approved terminology in one central place so everyone starts from the same terms.
){kind=icon}
Manage terms in one place
Define approved, discouraged, and non-translatable terms with the context teams need to use them correctly.
){kind=icon}
Share one glossary
Give product, marketing, support, and localization teams the same terminology to work from.
){kind=icon}
Onboard contributors faster
Give translators, writers, and reviewers immediate access to approved terms and usage guidance.
What is a glossary?
A glossary is a centralized term base that defines approved terminology, discouraged or forbidden alternatives, translations, and usage guidance. It gives translators, reviewers, and AI the same terminology rules across projects and languages.
For managers
Reduce terminology-related revision and feedback cycles
Keep product terminology aligned across projects and teams
Maintain one source of truth for naming conventions
For marketers
Keep product names consistent across campaigns and markets
Align website, campaign, and product terminology
Give contributors approved wording from the start
For translators
Access approved terminology and context while translating
See preferred, discouraged, and non-translatable terms
Spend less time resolving terminology questions during review
Term status and translation rules
Mark terms as preferred, admitted, not recommended, or obsolete, and define whether they should always, never, or optionally be translated.
Rich term details
Add context, number, gender, and product-specific guidance so terms are used correctly.
Smart matching
Choose exact, fuzzy, prefix, or custom matching and control case sensitivity for each term.
Multilingual entries and priorities
Add translations for each locale and define priorities when several glossary entries could apply.
01
Control glossary access
Assign ownership and permissions so glossary changes stay with the people responsible for terminology.
02
Surface terms while translating
Show approved glossary matches directly in the Editor, where translators and reviewers can apply them.
03
Import and export terminology
Import existing terminology from CSV and export glossary data in CSV or TBX formats.
04
Reuse terms across locales
Set fallback languages to reuse terminology when a locale-specific translation is not available.
Define terminology once. LINA and your team use it wherever the glossary applies.
Create or import your terms
Add terms manually or import an existing glossary to build your terminology base.
Define how each term is used
Set matching, case sensitivity, translation rules, alternatives, and context.
Use the glossary in translation
LINA, translators, and reviewers work with the same approved terminology when new content is translated.
Language you can ship. Start localizing now.
Free 14-day trial. No credit card required.
Glossary, translation memory, and QA on every string.
LINA drafts. Your team approves what matters.
The next release matches the last one.
Got questions? We have the answers.
How do I control which terms are used and which are avoided in LingoHub?
Categorize terms as “Preferred”, “Admitted”, or “Not Recommended” to enforce top choices and flag obsolete wording. You can also mark specific brand names to never be translated to ensure global consistency.
How does the glossary reduce manual review cycles?
Smart matching automatically surfaces approved terms in the editor, ensuring translators use correct wording instantly. This prevents terminology errors at the source and significantly reduces the need for manual review loops.
Can I manage different terminology in LingoHub for multiple brands?
Use project-specific glossaries alongside a global term base to manage distinct naming conventions for different products. Role-based permissions and approval workflows keep these updates secure across all departments and vendors.
