Skip to main content

How to Configure and Use UI Term Replacement based on Glossary

All you need to know about UI Term Replacement based on Glossary


Table of Contents


What is Term Replacement based on Glossary?

The UI Term Replacement based on Glossary feature automates the replacement of User Interface (UI) terms during the pre-translation process. By identifying terms wrapped in specific tags, the system cross-references your configured glossaries to ensure absolute terminology consistency.


Configuration (Advanced Settings)

This advanced functionality is managed directly within your glossary settings for streamlined workflow integration:

How to enable:

  • Go to the desired Organizational Unit or Project.

  • Navigate to the Context tab.

  • Locate the glossary you wish to use for UI replacement.

  • Select Advanced Settings.

Available Parameters:

  1. UI Term Replacement: Turn the functionality on or off for the specific scope.

  2. Tag names: Define multiple tags that will trigger the replacement logic (e.g., uicontrol , userinput).


Replacement Logic & Expected Behavior

Once configured, the replacement logic is executed immediately following the Pre-translate step. When you open a task in the Editor, the system will have already scanned the source text for your specific tags and applied the following behaviors:

Scenario: No Match in Glossary

System Action: The term remains in the Source language. The rest of the segment is translated normally.

Editor Feedback: Smell Alert: No glossary translation found for this UI term.

Scenario: Single Match

System Action: The term is automatically replaced by the exact glossary suggestion in the target.

Editor Feedback: Segment is pre-translated

Scenario: Multiple Matches

System Action: The term remains in English/Source to prevent incorrect automated choices.

Editor Feedback: Smell Panel expands below the segment, displaying the multiple glossary matches.


Scope of Application

Settings can be managed at two levels to balance global consistency with local flexibility:

  • Organizational Unit Level: Sets the terminology standard for an entire department or specific client.

  • Project Level: Allows project managers to override or fine-tune settings for specific localization tasks.

Did this answer your question?