Context Sensitive Translate is wxrks's AI translation action for a single segment — it blends your Translation Memories, Machine Translation output, and Glossaries into one suggested translation, tailored to the segment you're actually working on rather than a generic machine translation. It runs automatically the moment you open an empty segment, and you can also trigger it yourself at any time.
​

💡 Who is this for? This guide is for any user with Editor access who needs to use Context Sensitive Translate to auto-translate empty segments and refresh AI suggestions while translating or reviewing within the wxrks platform.

Context Sensitive Translate doesn't just pick one source and use it as-is — it looks at all three at once and produces a single suggestion informed by whichever ones actually apply to that segment:
​

You don't have to guess which of these shaped a given suggestion — turning on Translation Reasoning on the card shows exactly which factors influenced that specific translation.

With Enable Context Sensitive Translate on in your Editor Settings panel, opening a segment that has no target text yet triggers an AI translation automatically — you don't need to click anything. This also applies to a segment that only looks empty because it was created by merging two segments together; wxrks still treats it as empty and auto-translates it the same way.

If your account, Organizational Unit, or your own Editor preferences don't already have Augmented Actions enabled, opening an empty segment won't trigger anything — see wxrks Augmented Actions for the full three-level (Account, Organizational Unit, User) enablement walkthrough.

Two ways to get a fresh (or first) Context Sensitive Translate suggestion without waiting for the automatic trigger:

If a segment already has a translation, click into it and select Refresh on the Context Sensitive Translation card to have the AI reconsider it — worth doing whenever a TM, glossary, or MT setting has changed since the segment was last translated, since Context Sensitive Translate otherwise keeps working from what it saw at the time.

Selecting any segment reveals an Augmented Actions button in its bottom-right corner. Its dropdown menu includes Context Sensitive Translate — selecting it runs the exact same underlying translation as the automatic and Refresh cases above, just triggered manually on whichever segment you have selected, translated or not.

For the other actions in this menu — Alternative Suggestion, Proofread, Check Smells, Fix Tags — see wxrks Augmented Actions.

Once a segment has a Context Sensitive Translation, a Translation reasoning switch appears directly on that card. Turning it on shows the rationale behind the suggestion as a short set of categorized bullets — for example GLOSSARY ENFORCEMENT for a specific glossary-driven word choice, or FLUENCY ADAPTATION for how the wording was adjusted to read naturally in the target language. Other categories appear when they apply — TM Reuse, Audience/Tone, Terminology Choice, Style Adjustment, Localization, Error Correction, Formatting — only the factors that actually influenced that translation are shown.
​

Translation reasoning is off by default and, once you turn it on, stays on for you across segments and sessions. Turning it on for a segment that already has a translation refreshes that translation immediately so the reasoning appears. See Translation Reasoning for the full walkthrough of every category and why you'd turn it on.

Augmented Term Lookup is a separate, independent feature — it runs on its own as soon as you open a segment containing an inflected form of a glossary term, surfacing suggested variants in the Editor's GLOSSARY VARIANTS panel. It never feeds into or changes Context Sensitive Translate's own output, and nothing it suggests is applied automatically.
​

In practice this means a segment can show two different forms of the same word at once: Context Sensitive Translate might produce a literal, unadapted glossary substitution, while Glossary Variants separately offers a better-inflected form as its own suggestion. If you want the inflected form instead of what Context Sensitive Translate produced, apply the variant yourself from that panel — it's never applied for you.

Opening an empty segment doesn't trigger anything. Confirm Augmented Actions is enabled at all three levels — Account, Organizational Unit, and your own Editor Settings panel's Enable Context Sensitive Translate toggle. See wxrks Augmented Actions for where each toggle lives.

The card shows a TM badge instead of a fresh AI translation. This is expected, not a bug — the project has a strong enough Translation Memory match that wxrks reused it verbatim rather than generating a new suggestion. Select Refresh if you specifically want a fresh AI translation instead.

Still stuck? Search the wxrks Community forum or contact [email protected].