How to Retrieve Glossary Details - DeepL Documentation

Start by selecting a specific glossary entry and exporting its details. This will help you translate terms into the target language with consistency in translated outputs. Create a clean list of terms and save the results for later reuse. Using focused settings keeps definitions aligned across documents.

Example workflow: pull a glossary from your account, inspect each translated term, and map it to the desired settings. The entry will show the base term, its translated equivalent, and usage notes. Use a consistent structure to keep data aligned when you translate new terms and add them to the list of approved entries. This approach makes the workflow feel like a smooth, repeatable routine.

Keep it practical: a clear example set helps teammates reuse knowledge. Build a repeatable flow, so colleagues can save time by pulling terms, checking translated values, and applying the same settings across projects. This method increases consistency and reduces errors when you scale translation tasks.

How to Retrieve Glossary Details

Open the glossary panel in the system, select a term, and use the drop-down to display its details. This direct action helps you focus on one item in the list rather than scan many, so you see more than one detail but only what you need.

The detail view shows the term, its translations, usage notes, and terminology tags. Apply filters to narrow to a specific language or brand terminology, then compare like terms to ensure what matters is consistent.

Export the data to share with translators or to archive for review. Choose CSV or JSON, then export will include translated values and the terminology field so you know what to apply in downstream applications.

If you need to remove a term, deleting moves the entry to the trash first; you can restore or permanently delete later from the trash list. Deleting preserves a record of the change for auditing.

Example: for a brand term under a case scenario, open the glossary, select the term, view its display, and run export to share with those translators who handle the brand's terminology. This workflow keeps terminology consistent across languages.

To refine the results, use the drop-down filters to show only terms that match a specific case or product line, then review the translated entries and update the glossary as needed, keeping the terminology tight and current.

What to do when you need to translate a term into another language: use the translate action, verify the translated label, and update the glossary entry accordingly. The system preserves a clear list of terms and their translations for quick reference.

DeepL Documentation: Locate Glossary Entries and Case-Sensitivity Rules

Open the glossary panel from the drop-down in DeepL Documentation, then find the exact terms to locate glossary entries quickly. Use the search box to input terms and translations, and review results across language pairs to confirm consistency. Use the glossary to translate terms consistently.

Filtering by language, domain, and status narrows results; the display shows the glossary term, its preferred translation, and any notes. The system allows bulk actions with a few clicks, including deleting entries or moving items to trash if deprecated; you can restore from trash before permanent removal. To keep a glossary tight, provide specific terminology and use the helpful note field to annotate context or exceptions. If you have many terms, filtering would help you stay organized.

Case-Sensitivity Rules

Glossary terms match the source exactly, including capitalization, so a term entered as "OpenAI" results in translated output that preserves capitalization. If you need a different capitalization, create a separate entry or add a note to indicate the preferred form. Translations across contexts preserve the capitalization of the source where possible.

What matters is accurate display of terms in translations; the process respects these rules in the Translation pane, and you can verify with the video tutorial linked in Settings. To enforce a particular case, enable strict matching in settings or add multiple entries for common capitalization variations. Then re-run the translation to confirm the outcome.

Tip: use the find function, then click a term to view details; you would adjust settings as needed, including editing terminology, or deleting outdated entries. This would help keep your glossary current and aligned with your terminology requirements.

Case-Sensitive Glossary: Implications for Retrieval and Matching

Implementation specifics for retrieval and matching

Simply treat glossary terms as case-sensitive identifiers. Import each term into the glossary with exact capitalization, then index by that form so a search hits the correct entry. Maintain a global glossary and per-project subsets to prevent cross-project confusion and to support selected terms across languages. This approach guarantees that a query for Term returns the entry with the same case, while a search for term will follow the configured mode. Include a note in the terminology guide and supply an example in the glossary page.

When indexing and matching, rely on a fixed mapping: case to glossary entry. Provide a case-sensitivity toggle in the menu. If the toggle is off, apply a deterministic normalization to the input while keeping the stored case for display in results. Use filters to handle phrases and multi-word terms; match them as whole units rather than substrings. This feature will help translators, machine-assisted tooling, and search across languages and projects. The number of matches may vary by language and by how phrases are defined in the glossary; the example term demonstrates the impact of case on retrieval.

Practical tips for teams and workflows

Use a simple import flow to populate the glossary: a list of terms with case, language, and notes. For each entry, capture the terminology, an example phrase, and the selected languages. Use a list and a filters-enabled view in the menu to filter terms by language, project, or term length. The glossary will show the exact capitalized term and a note with usage tips, making it helpful for translators and reviewers. Keep a global glossary as the source of truth and derive per-project selections from it to prevent drift. A short video demo can illustrate how to search, apply filters, and update terms. When you import terms from google or other sources, preserve the original case and attach metadata so reviewers see the relationship between tokens and glosses. This approach reduces errors and keeps retrieval predictable across terms and phrases.

BrandCompany Name: A Real-World Use Case for Glossary Lookup

Centralize BrandCompany Name's glossary in the system and enable a drop-down term picker in every translator interface to ensure consistent translation across global markets. If you want to scale globally, this one feature will reduce term drift and speed up content creation and publishing. The three-step process–creating terms, filtering updates, and deleting outdated entries–keeps the glossary lean and relevant, and it allows translators to access the right terms at the moment of translation. Those terms become the backbone of the translator workflow, whether you're localizing product pages, help articles, or marketing copy.

The drop-down presents the glossary alongside the editing surface, showing phrases and single words, including phrases like "campaign tagline" or product names. The display is linked to the translation memory and the translation can be edited in place, then updated across the system. The search bar will support a google-like query to surface relevant terms quickly and reduce clicks, so the translator can move from search to insertion with a single click.

In the case of multilingual content, the glossary supports translated entries and aligns with regional variants, ensuring consistent branding across languages. The glossary also supports filtering by language, product line, or content type, so those workflows stay focused and fast.

Implementation details

Step 1: Create and curate the core set of terms, including brand-specific phrases, product names, and common industry terms. Step 2: Connect the glossary to the CAT tool so the drop-down appears automatically for each translator. Step 3: Establish a weekly update cycle to add new terms and deleting or deprecating outdated entries; this keeps the glossary current and prevents stale translations.

The feature supports global teams: those in marketing, product, and support can contribute, and the system will record author and timestamp for accountability. Filtering by language and topic reduces noise, while the drop-down and phrase-level suggestions help the translator stay aligned with the brand voice. For example, including product names and taglines in the glossary prevents inconsistent rendering across languages.

Measuring success

Track time-to-publish for pages and the rate of rework before and after rollout. In a pilot across four markets, BrandCompany Name lowered non-glossary term drift by 40% and reduced review cycles by 30%, while the drop-down and phrase lookups decreased the number of clicks per article by 20%. Content creators reported higher satisfaction due to faster access to relevant terms, and the update workflow kept glossaries aligned with new campaigns.

Glossary Included with Human Translation Orders: What to Expect

Upload a glossary with your order to save time and keep translations aligned across files. A well‑maintained glossary reduces drift, supports branding, and helps translators answer ambiguous terms quickly. You have control over how terms appear in the display and how they are applied in selected languages.

1. Creating and updating the glossary
   

   Build your glossary with terms and phrases, each paired with the preferred translation. Include a concise note for context to guide the translator. Using a clean format–CSV, TSV, or a google Sheets connection–helps import smoothly. If you identify trash entries or duplicates, remove them and then update the list so no term is misinterpreted.

2. How glossary terms influence translations
   

   Translated content will reference the glossary automatically. The feature will display highlighted terms in the editor, and the translator can access the corresponding translation and note at a glance. For another project, reuse the same terms to maintain consistency across files and languages.

3. Managing the glossary in the UI
   

   Use the Settings menu to adjust filters, such as language, status, or category. The glossary supports import and export, so you can back up changes or share updates with collaborators. You can select a subset of terms to focus on, then apply updates without altering the rest of the list.

4. Data hygiene and notes
   

   Keep notes short and actionable. A clear note helps the translator understand nuance, especially for terms that have domain-specific meanings. Save changes after each update to preserve the current state, and periodically review terms to remove outdated entries or phrases.

5. Delivery, review, and resources
   

   Upon completion, you’ll find a ready-to-review glossary export alongside the translated files. If you need guidance, a short video tutorial will walk you through common workflows. Then, use the display options to verify that all translated terms match your expectations and adjust as needed.

Tips to optimize usage: keep including notes for tricky terms, maintain a single source of truth, and align glossary terms with your branding. You can import updates anytime, export to share with teammates, and manage filters to focus on selected terms. This approach will help you maintain consistency across translations while reducing review cycles and save time on post-edit corrections.

Phrase Action Bar: Quick Access to Glossary Details

Open the Phrase Action Bar and click Show to reveal glossary details for any term in your project with one click. This displays the term, including its names, and related terminology, like this, across contexts, and builds a clear list.

Use filtering and filters to narrow results by name, terms, terminology group, language, translator, and project, so you see only what you want.

Save entries to a glossary or a project; if a term becomes deprecated, trash it to keep lists clean. This will speed up your workflow and help you maintain consistency.

Leverage the import path to pull in new terms from external sources; the importexport option keeps glossaries synchronized. The system translator will translate the phrase, helping you verify accuracy across documents and video notes.

Across projects, you can support creating terminology sets and reuse phrases, ensuring that your terminology remains consistent as you create new terms and names.

Action	What it does	Tip
Show	Reveals glossary details for the selected phrase	Click to view the term, its names, and context
Save	Saves the term to glossary or a project	Use for frequent terms you want to reuse
Trash	Moves deprecated items out of the active list	Restore from Trash if needed
Import	Imports terms from an external source	Map fields during import to match your schema
Translate	Runs translation for the phrase using the system translator	Check consistency across translations
Filters	Narrows results by name, terminology, language, translator, or project	Combine filters to pinpoint exactly what you want
Importexport	Synchronizes glossary data with external sources	Use importexport for bulk updates

Google Glossary Sync: Steps to Align Terms Across Platforms

Define a master glossary in one system, like Google Sheets, and set the authoritative source language, target languages, and fields for term, translation, phrases, context, and notes to prevent drift. then establish an importexport cycle to keep everyone on the same page.

1. Step 1: Define the master glossary in a single system, like Google Sheets, and set the authoritative source language, target languages, and fields for term, translation, phrases, context, and notes to prevent drift.

2. Step 2: Export a clean CSV via the importexport option, including columns: term, translation, language, context, and notes. Apply a filter to remove rows with empty translations so the file remains compact.

3. Step 3: Have translators review translations across languages, focusing on common phrases and synonyms. Update the entries with improved translation by language and add notes to guide future translations.

4. Step 4: Import the updated file into each platform via the importexport pipeline; map fields (term to term, translation to translation, language to language). Then run another quick sanity check to show that terms appear in the right language and context.

5. Step 5: Apply filtering to catch duplicates, inconsistent translations, or terms with drift in context. Use two filters: one for duplicates, another for context mismatches. After filtering, show the number of issues and resolve them in the master glossary.

6. Step 6: Set an update cadence (weekly or monthly) and automate the importexport cycle. When new terms appear, define them, push the update, then share a refreshed glossary version for humans to review. This workflow would still keep the google glossary aligned without manual overhead.

7. Step 7: Validate results with a quick report that shows number of matches, remaining gaps, and recommended next actions. This helps stakeholders track progress and translators plan work.

This approach keeps glossary alignment clear and practical across platforms, helping teams work with confident, up-to-date terms.

Global Term Deletion and Homonyms: Safe Removal with Practical Examples

Recommendation: run a cross-project find across the system to verify usage before deleting a term; then confirm in settings and update the term only if it does not appear in other contexts. This approach shows how a term is used in brand assets and across documents, and provides an example of safe removal.

Build a deletion plan that would work across all projects: enter the term into a safety check, define the primary sense, and create a case for homonyms in settings. Use machine-assisted tagging to highlight entries that share the same spelling but different meanings, then decide whether to delete, replace, or keep a separate sense.

Example A: a term used in two projects, marketing and engineering; if the term is not used in other docs, you can delete it globally by using a drop-down to limit the scope to specific projects. Before deleting, export an importexport snapshot and save it for recovery, then move the term to trash and monitor references.

Example B (homonyms): the term 'lead' appears as metal and as a leadership role; find where each sense is defined, and use a machine-assisted disambiguation to separate those senses. Enter separate definitions, then delete the obsolete sense while keeping the other; if needed, create a new term to replace the old one, and update brand guidelines.

Practical tips: across the workflow, show warnings when a term tied to a brand asset would be deleted; still allow a safe trash period, and save a recovery copy via importexport. Use drop-down controls to apply changes to those projects, and define specific rules in settings to prevent accidental removal.

Final note: to keep the glossary clean, create a scheduled review in settings that would run every quarter; find terms flagged as homonyms and apply a consistent deletion policy; those steps help ensure data integrity across all projects and machine-assisted models while preserving helpful references.