Define a term with boundaries
Make a product term useful by explaining its concept, preferred wording, and the cases where it does not apply.
A glossary is most useful when a translator can recognize the concept behind an entry. A source word and preferred target word may be enough for a unique name. For an ambiguous term, the entry also needs to explain where that meaning applies.
Start with a term the team has disagreed about. Gather its source sentence, surrounding content, existing translations, target locale, and the person responsible for its product meaning. Resolve that meaning before treating spelling as the whole decision.
Define the concept and its boundary together #
Consider “workspace.” It can name a shared area in software or a physical place to work. An illustrative product entry could contain:
| Part | Example |
|---|---|
| Concept | A shared product area containing a team's projects and membership. |
| Applicable contexts | Navigation, settings, invitations, and help about that product area. |
| Exclusion | A desk, workshop, or physical office area. |
| Locale wording | The rendering approved by qualified reviewers for each locale. |
| Intended-use case | “Invite a colleague to your workspace.” |
| Counterexample | “Keep your physical workspace clear of cables.” |
This is a planning record, not a glossary API schema. Its purpose is to let another person decide whether the entry applies. Leave target wording unresolved until someone qualified can approve it instead of inventing a translation to complete the table.
Decide how the term behaves in a sentence #
A fixed product name may need to remain unchanged. A translated concept may need inflection to fit the surrounding grammar. Explain the intended treatment and its reason; typography alone does not tell a translator whether a term can change form.
Record regional differences deliberately. The product concept can remain the same while preferred wording differs between locales. A nearby locale offers material for review, not automatic equivalence.
Store the decision without creating a competing definition #
Use Glossaries to inspect the existing entry, hint, locales, and localization-engine attachments. Update an existing record when it describes the same concept. If a common glossary serves products with different meanings, a separate resource or narrower scope may be more appropriate than changing every consumer.
The hint guides interpretation, while retrieval determines whether the term reaches a request. Neither saving the entry nor attaching the glossary guarantees that the model will use it correctly. Preserve the expected sense and the excluded sense so both can be tested.
Test the distinction, not only the preferred word #
Keep earlier output for the product sentence and physical-workspace counterexample. Change only the term guidance, confirm the saved record, and translate those cases through the intended workflow. Include a grammatical variation and a short interface label if the real product uses both.
The product example should use the approved concept and target wording. The physical example should retain its ordinary meaning. If only the preferred spelling is counted, a check can miss the error of applying it to the wrong concept.
When a case fails, check the saved term, locale coverage, engine attachment, and submitted context before adding synonyms. A short source label such as “Space” may need a usage hint or surrounding context. The repair can be better information about the source rather than a larger glossary.
Keep the decision usable after a product change #
Retain the approver, tested contexts, and localization engines using the term. If the product concept changes, update its definition and inspect existing translations separately. A glossary edit does not repair every catalog retroactively.
Update one key or term safely develops a bounded refresh. The same intended and excluded examples can support measurement design. A complete term definition lets a reviewer explain both when to use it and when to leave it out.