Supervertaler for Trados: Docs for the Trados Studio plugin only # Supervertaler for Trados Supervertaler for Trados is a plugin for **Trados Studio 2024+** that brings Supervertaler’s terminology and AI features directly into the Trados editor. It runs natively inside Trados Studio as a set of dockable panels, so you never have to leave the editor. ![]() ### Getting Started Screencast New to Supervertaler? Watch the [Getting Started screencast](https://www.youtube.com/watch?v=bOIwMAoP7xc) (16 min) for a walkthrough of all the basics – TermLens, prompt generation, AI translation, the Chat window, and more. [Supervertaler for Trados – Getting Started (16 min)](https://www.youtube.com/embed/bOIwMAoP7xc) ### Key Features #### TermLens (Inline Terminology) Live terminology display that shows the source text word by word, with termbase translations underneath each matched term. Colour-coded by termbase type: * **Blue** for regular termbase matches * **Pink** for project termbase matches (higher priority) * **Yellow** for non-translatable terms * **Green** for MultiTerm termbase matches (`.sdltb` files attached to your Trados project, or `.ttb` termbases in Trados Studio 2026) Numbered badges let you insert terms with **Alt+1** through **Alt+9**. Project termbases are detected automatically from your Trados project and are read-only. On Trados Studio 2026 these are the new `.ttb` termbases –see [Trados Studio 2026 & .ttb](/trados/studio-2026/). #### Supervertaler A conversational AI chat panel that is aware of your current segment, matched terminology, and TM matches. Ask questions about translation choices, get alternative phrasings, or request explanations –all without leaving Trados. #### Batch Translate Translate multiple segments at once using AI. Choose a scope (empty segments, all segments, filtered segments), pick a prompt, and let the AI work through your file. Progress is shown in real time. #### Prompt Library A built-in Default Translation Prompt and Default Proofreading Prompt to get you started, plus QuickLauncher prompts for common tasks. Create your own custom prompts in the Prompt Manager – duplicate the default and tailor it to your domain. #### Termbase Management Create, edit, and import termbases in Supervertaler’s `.db` format. Quick-add terms with keyboard shortcuts, mark terms as non-translatable, and manage multiple termbases per project. #### SuperMemory The client decisions you cannot look up: which term they insist on, what they rejected last time, how they want things phrased. Each memory bank is three Markdown files you write and edit yourself - a brief, a terminology table, and style rules - plus a shared bank of house defaults that every client bank can override. The AI reads the active bank on every translation. Keep one bank per client or domain and switch from the toolbar dropdown; add a term while translating with Ctrl+Alt+M. [Learn more →](/trados/ai-assistant/super-memory/) ### System Requirements | Requirement | Version | | -------------- | ------------------- | | Trados Studio | 2024 (v18) or later | | Windows | 10 or 11 | | .NET Framework | 4.8 | There are two builds: one for **Trados Studio 2024** (MultiTerm `.sdltb` termbases) and one for **Trados Studio 2026** (`.ttb` termbases). Install the build that matches your Studio version –see [Trados Studio 2026 & .ttb](/trados/studio-2026/). ### Shared Termbase Format Supervertaler for Trados uses the same SQLite-based termbase format (`.db`) as [Supervertaler Workbench](https://docs.supervertaler.com/workbench/). Termbases created in either tool are fully compatible – you can open the same `.db` file in both applications. ### Context-Sensitive Help Press **F1** at any time to open context-sensitive help for the panel or dialogue that currently has focus. ### Next Steps | | | | ---------------------- | ------------------------------------------------------------- | | **Installation** | [Install the plugin →](installation.md) | | **Getting Started** | [Set up termbases and AI →](getting-started.md) | | **TermLens** | [Inline terminology display →](termlens.md) | | **Supervertaler** | [Chat with AI in Trados →](ai-assistant.md) | | **MultiTerm Support** | [Use MultiTerm termbases in TermLens →](multiterm-support.md) | | **Batch Translate** | [Translate segments in bulk →](batch-translate.md) | | **Keyboard Shortcuts** | [All shortcuts at a glance →](keyboard-shortcuts.md) | # Supervertaler Assistant The Supervertaler Assistant is a conversational chat panel that runs inside Trados Studio as a separate dockable panel. It is context-aware: it automatically includes your current source and target text, matched terminology, and TM matches in every request, so the AI can give you informed answers about the segment you are working on.  ## Opening the Panel The Supervertaler Assistant lives in its own dockable panel. To open it, go to **View > Supervertaler Assistant**. You can dock the panel on the right side, bottom, or as a floating window. Trados remembers the panel position between sessions. ## Chat Type a message in the input field at the bottom and press **Enter** to send. The AI will consider your current source text, target text, matched terminology from your termbases, and TM fuzzy matches when responding. | Action | How | | --------------------------- | ------------------------- | | Send a message | Press **Enter** | | Insert a line break | Press **Shift+Enter** | | Stop a response in progress | Click the **Stop** button | ### What You Can Ask Because the assistant has access to your current segment context, you can ask things like: * “Translate this segment” * “What is the difference between these two translations?” * “Is this terminology correct in a legal context?” * “Suggest a more formal alternative” * “Explain this source text” ### Chat History The conversation is saved automatically after every message and restored the next time Trados starts. Your history persists until you explicitly clear it. To clear the history, click the **Clear** button in the chat toolbar. ### Right-Click Menu Right-click any assistant response bubble to access: | Action | Description | | ----------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Copy** | Copies the raw Markdown to the clipboard, preserving tables and formatting | | **Apply to target** | Inserts the plain text (Markdown stripped) into the active target segment | | **Save as Prompt…** | Saves the response as a reusable prompt template | | **Save to memory bank** | Saves the question + response into the active bank’s `reference/` folder so a useful answer is not lost. Nothing reads it automatically - fold anything worth keeping into `brief.md`, `terminology.md` or `style.md`. | If you select text within a bubble before right-clicking, **Copy** and **Apply to target** operate on the selection only. ## Features | Feature | Description | | ---------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | | [**Context layers**](/trados/context-layers/) | The ten layers of context sent with every request – project, segment, TM, terminology, SuperMemory, list numbering, figures | | [**File Attachments**](/trados/ai-assistant/file-attachments/) | Attach images and documents (PDF, DOCX, XLSX, TMX, etc.) for additional context | | [**Studio Tools**](/trados/ai-assistant/studio-tools/) | Query your Trados Studio projects, TMs, termbases, and statistics using natural language | | [**Incognito Mode**](/trados/ai-assistant/incognito-mode/) | Anonymise project names, file paths, and personal data in AI responses for safe sharing | | [**Providers and Models**](/trados/ai-assistant/providers/) | Supports 7 AI providers including OpenAI, Claude, Gemini, Grok, Mistral, Ollama, and custom endpoints | | [**Supervertaler Bridge**](/trados/ai-assistant/supervertaler-bridge/) | Localhost-only HTTP service behind the [MCP Server](/trados/mcp-server/): how Claude Desktop and other AI apps read and write your live Trados project | ## See Also * [QuickLauncher](/trados/quicklauncher/) – One-click prompt shortcuts * [Batch Translate](/trados/batch-translate/) – Translate multiple segments at once * [AI Settings](/trados/settings/ai-settings/) – API keys, model selection, context options * [Keyboard Shortcuts](/trados/keyboard-shortcuts/) # Chat The **Chat** tab is the conversational heart of the Supervertaler Assistant – a context-aware chat that already knows your current segment, its terminology and TM matches, so you can ask questions and get answers grounded in the document you are translating. (See the [Overview](/trados/ai-assistant/) for opening the pane and the basics of chatting.) Two features extend what a chat can do: * **[File Attachments](/trados/ai-assistant/file-attachments/)** – attach images or documents (a reference PDF, a style guide, a screenshot of the source layout) to a message for the AI to use as context. * **[Studio Tools](/trados/ai-assistant/studio-tools/)** – ask the assistant about your Trados installation in plain language (projects, translation memories, termbases, templates) and it looks the answer up for you. # File Attachments The Supervertaler Assistant supports attaching both images and documents to your messages. Use the **paperclip button** next to the chat input, or drag and drop files directly onto the chat area. ## Images Attach images for visual context – for example, a screenshot of the source document layout, a reference image, or a table that is hard to describe in text. Images are sent to the AI using each provider’s native vision API. | Method | How | | ------------- | --------------------------------------------------- | | Paste | Press **Ctrl+V** with an image on the clipboard | | Drag and drop | Drag an image file into the chat input area | | Browse | Click the paperclip button and select an image file | Supported image formats: PNG, JPEG, GIF, WebP, BMP. Up to **5 images** per message, **10 MB** maximum per image. ## Documents Attach documents to provide the AI with additional reference material – for example, a client style guide, a termbase in spreadsheet form, a reference PDF, or a translation memory export. The text content is automatically extracted from the document and included in your message as context. | Method | How | | ------------- | ----------------------------------------------------- | | Drag and drop | Drag a document file into the chat input area | | Browse | Click the paperclip button and select a document file | The chat bubble shows a compact summary (file name and size) instead of the full extracted text, keeping the conversation readable. ### Supported Document Formats | Category | Formats | | ----------------- | ------------------------------ | | Documents | DOCX, DOC, PDF, RTF | | Presentations | PPTX, PPT | | Spreadsheets | XLSX, XLS, CSV, TSV | | Translation files | TMX, SDLXLIFF, XLIFF/XLF, TBX | | Text and markup | TXT, Markdown, HTML, JSON, XML | ## See Also * [Supervertaler](/trados/ai-assistant/) – Overview * [Context layers](/trados/context-layers/) – What context is sent automatically # How the assistant works Whatever you do in the Supervertaler Assistant – chat, a batch translation, a proofread, or an AutoPrompt – it works the same way under the hood: it gathers **context** from your project and sends it to an **AI provider**, then returns the result. These pages explain what the AI sees and how to control it: * **[Context layers](/trados/context-layers/)** – exactly what Supervertaler puts in front of the AI, in ten layers (current segment, surrounding segments, terminology, TM matches, SuperMemory, the document’s list numbering, descriptions of its figures) and how to tune how much is included. * **[Providers and Models](/trados/ai-assistant/providers/)** – which AI you talk to (Claude, OpenAI, Gemini, local models …), and how to set up your API key and choose a model. * **[Incognito Mode](/trados/ai-assistant/incognito-mode/)** – a privacy filter that anonymises project names, file paths, TM names and other identifying data in the AI’s responses, so you can screen-share, record or post screenshots without exposing client information. # Incognito Mode Incognito Mode tells the AI to **anonymise all personal and project data** in its responses. When enabled, project names, file paths, TM names, user names, and other identifying information are automatically replaced with plausible placeholders – so you can share your screen, record videos, or post screenshots without worrying about exposing confidential client data. 🕵️ Think of it as a privacy filter for your AI chat. ## When to Use It | Scenario | Example | | ------------------------ | ----------------------------------------------------------------------------- | | **Screen sharing** | Presenting to colleagues or in a webinar while working on a real project | | **Recording demos** | Making tutorial videos that show real workflows without real client names | | **Forum posts** | Sharing a helpful AI response in a community without revealing client details | | **Client presentations** | Showing how the tool works without exposing other clients’ data | | **Training** | Onboarding new team members on live projects | ## How It Works When Incognito Mode is enabled, the AI receives an instruction to replace all identifying data with anonymised equivalents. For example: | Real data | Anonymised | | ---------------------------- | -------------------------------------- | | Acme Corporation | Client Alpha | | D:\Jobs\ACME\Q1\_report.docx | D:\Projects\Client Alpha\document.docx | | Jane Smith | User A | | ACME\_NL-EN.sdltm | Client\_Alpha\_NL-EN.sdltm | The AI uses **consistent replacements** within a conversation, so if “Acme Corporation” becomes “Client Alpha” in one response, it stays “Client Alpha” throughout the session. ### What is NOT anonymised Some data is left untouched because it carries no identifying information: * Language codes (en-GB, nl-NL, de-DE, etc.) * Segment counts, word counts, and statistics * Translation status values (draft, translated, approved, etc.) * The actual source and target text you are translating * Technical identifiers (tool names, status labels) ## Enabling Incognito Mode 1. Open **Settings** (gear icon in the Assistant toolbar) 2. Go to the **AI Settings** tab 3. Scroll down to **Context layers (Chat and QuickLauncher)** 4. Tick **Incognito mode** 5. Click **OK** The setting takes effect immediately on your next message. Toggle it off when you no longer need anonymisation. ## Limitations * Incognito Mode instructs the AI to anonymise data in its **responses**. It does not prevent data from being sent to the AI provider – your source text, TM matches, and terminology are still included in the prompt as usual. If you need to prevent data from being sent entirely, disable those context options individually in AI Settings. * The AI does its best to catch all identifying information, but it cannot guarantee 100% coverage. Always review responses before sharing publicly. * [Studio Tools](/trados/ai-assistant/studio-tools/) results (project lists, TM searches, etc.) are also anonymised – the AI receives the real data from the tools but presents it with placeholder names. ## See Also * [Supervertaler](/trados/ai-assistant/) – Overview * [AI Settings](/trados/settings/ai-settings/) – Configure context options and Incognito Mode * [Context layers](/trados/context-layers/) – What context is sent to the AI # Providers The Supervertaler Assistant supports multiple AI providers. You only need one to get started. ## Switching Models The current provider and model are shown in the status area at the bottom of the chat panel. You can switch models in two ways: * **Quick switch** – click the provider/model label directly. A dropdown menu appears with all available models grouped by provider. The current model is marked with a tick. Select a different model to switch instantly. * **Settings** – open the settings dialogue (gear icon) and switch to the **AI Settings** tab for full configuration including API keys, endpoints, and advanced options. ## Supported Providers | Provider | Models | | -------------- | -------------------------------------------------------------------------------- | | **OpenAI** | GPT-5.5, GPT-5.4 Mini | | **Anthropic** | Claude Sonnet 4.6, Claude Haiku 4.5, Claude Opus 4.8 | | **Google** | Gemini 3.1 Flash-Lite, Gemini 2.5 Pro, Gemini 3.1 Pro (Preview), Gemma 4 26B MoE | | **Grok** | Grok 4.3 | | **Mistral** | Mistral Large, Mistral Small | | **DeepSeek** | DeepSeek V4 Pro, DeepSeek V4 Flash | | **OpenRouter** | Claude, GPT, Gemini, DeepSeek, and 200+ others via a single API key | | **Ollama** | TranslateGemma, Qwen 3, Aya Expanse (local, no API key needed) | | **Custom** | Any OpenAI-compatible API endpoint | ## Choosing a Model For everyday translation questions, a smaller and cheaper model like **GPT-5.4 Mini**, **Claude Haiku 4.5**, or **DeepSeek V4 Flash** works well. For complex tasks like document analysis, prompt generation, or when you need the highest quality suggestions, use a larger model like **Claude Sonnet 4.6**, **GPT-5.5**, or **DeepSeek V4 Pro**. Some features are provider-specific: | Feature | Availability | | ------------------------------------------------------------------------ | --------------------------------- | | [Studio Tools](/trados/ai-assistant/studio-tools/) | All providers except Ollama | | Image attachments | All providers with vision support | | Document attachments | All providers | | [Memory bank](/trados/ai-assistant/super-memory/ai-integration/) context | All providers | ## See Also * [Supervertaler](/trados/ai-assistant/) – Overview * [AI Settings](/trados/settings/ai-settings/) – API keys, endpoints, advanced options * [AI Cost Guide](/trados/ai-cost-guide/) – Token pricing and cost estimates # Studio Tools Studio Tools lets you query your Trados Studio installation using natural language in the Supervertaler Assistant chat. Instead of navigating through menus and dialogs, you can simply ask the assistant about your projects, translation memories, termbases, and project templates – and it will look up the answer for you. Caution Studio Tools is under active development and some commands might not yet work as expected. If something doesn’t work, please contact and I’ll get it working as fast as I can. ## How It Works When you send a message in the Supervertaler, the AI automatically decides whether it needs to query Trados Studio to answer your question. If it does, it calls the appropriate tool behind the scenes, reads the result, and presents the information in a clear format. You do not need to use any special syntax or commands. Just ask your question naturally. While a tool is running, the thinking indicator shows what is happening – for example, “Checking Trados projects…” or “Searching translation memory…”. ## Available Tools | Tool | What It Does | | -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **List Projects** | Lists all projects registered in Trados Studio with their name, status, and creation date. Supports filtering by status (in progress, completed, archived) | | **Get Project Details** | Shows detailed information about a specific project, including source and target languages, files, and folder path | | **Project Statistics** | Shows word count and analysis statistics for a project, broken down by match category (perfect, context, exact, fuzzy, new, repetitions) | | **File Status** | Shows the confirmation status of all files in a project – how many segments are not started, draft, translated, approved, or signed off | | **Project Termbases** | Lists termbases attached to a project, with their file paths, enabled/disabled state, and language index mappings | | **TM Info** | Shows detailed information about a specific translation memory, including language pair, segment count, file size, and creation date | | **Search TM** | Searches a translation memory for segments containing specific text. Returns matching source/target pairs so you can see how something was translated before | | **List TMs** | Lists all translation memories found in the Trados Studio TM folders | | **List Project Templates** | Lists all project templates available in Trados Studio | ## Example Questions Here are some things you can try asking in the Assistant chat: ### Projects * “What projects do I have in Trados Studio?” * “Show me all my in-progress projects” * “How many projects do I have?” * “Tell me about the Client Alpha project” * “What languages does the Client Alpha project use?” * “What files are in my latest project?” * “Do I have any completed projects?” * “Which project was created most recently?” ### Project Statistics and Progress * “What are the word counts for the Client Alpha project?” * “Show me the analysis statistics for my project” * “How many new words are in the Client Alpha project?” * “What is the fuzzy match breakdown for this project?” * “What is the translation status of the files in Client Alpha?” * “How many segments are translated vs. not started?” * “Which files still need work?” * “Are any files fully approved?” ### Termbases * “What termbases are attached to the Client Alpha project?” * “Show me the terminology resources for this project” * “Which termbases are enabled?” ### Translation Memories * “What translation memories do I have?” * “List my TMs” * “Tell me about the English-Dutch TM” * “How many segments are in my main TM?” * “How big is my TM?” ### TM Search * “Search my English-Dutch TM for ‘compliance’” * “How was ‘annual report’ translated before?” * “Find segments containing ‘data protection’ in the TM” * “Look up ‘user interface’ in my TM” ### Combined Questions You can combine Studio Tools queries with the assistant’s regular translation capabilities: * “What projects am I working on? And can you also translate this segment?” * “List my projects, then explain the terminology in the current segment” * “Search the TM for ‘privacy policy’ and suggest a translation for the current segment” The assistant handles the tool calls first, then continues with the rest of your question seamlessly. ## Technical Details Studio Tools reads data directly from your local Trados Studio installation. Specifically: * **Projects** are read from the `projects.xml` file in your Documents folder (e.g., `Documents\Studio 2024\Projects\projects.xml`). Project details, statistics, and file status are read from the individual `.sdlproj` files. * **Termbases** are read from the termbase configuration stored in each `.sdlproj` file. * **Translation memories** are found by scanning the `Translation Memories` folder and project folders. TM metadata and search use direct SQLite read-only access to the `.sdltm` files. * **Project templates** are found in the `Project Templates` folder. No data is sent to external services other than the AI provider. The tool results are passed to the AI as part of the conversation so it can format and present them to you. ## See Also * [Supervertaler](/trados/ai-assistant/) – The chat interface where Studio Tools is available * [AI Settings](/trados/settings/ai-settings/) – Configure your AI provider # SuperMemory > >- **SuperMemory** is where you write down the things about a client that you cannot look up: which term they insist on, which wording they rejected last time, how they want dates written, what the previous reviewer changed and why. A translation memory gives the AI your previous wordings and a termbase gives it approved pairs; SuperMemory gives it the *reasoning* – and reasoning is exactly what an AI cannot derive from the source text, so getting it wrong is a real error rather than a stylistic difference. Knowledge lives in **memory banks**: one folder per client, domain, or job, which you switch between from the Supervertaler Assistant toolbar. SuperMemory is one of several [context layers](/trados/context-layers/) the assistant consults, alongside termbases, translation memories, document content and segment metadata. ## A bank is three files Every bank contains the same three Markdown files, plus a folder for source material: | File | What goes in it | | ---------------- | -------------------------------------------------------------------------------------------------------------- | | `brief.md` | Who the client is and anything standing: language pair, register, house preferences, how far to trust the rest | | `terminology.md` | Term decisions, **one table**, one row each | | `style.md` | Prose rules and approved boilerplate – how things are phrased, rather than which term is used | | `reference/` | Source material, unmodified: style guides, PDFs, glossaries. Never sent to the AI | That is the whole structure. You are meant to open these files and edit them by hand – the **📂 Open folder** button in the toolbar is there for exactly that. ### Why terminology is a table A table is the format in which a *wrong* entry is findable. You can scan a hundred rows in half a minute and spot the one that says the wrong thing; you cannot do that with a hundred files. Since the only reason to keep notes is that you can check them, the format that makes checking possible is the one that matters. ```markdown | Source | Target | Scope | Note | |---|---|---|---| | voorkeursvorm | preferred embodiment | domain | Not "preferred form" – term of art | | drager | wearer | project | **Never** "carrier" | ``` **Scope** says how far a row travels – `project`, `client`, or `domain`. It doubles as a promotion queue: a row that turns out to hold for a *second* client belongs in the shared bank. ### `reference/` is the audit trail Everything in the three files is *derived* from something – a style guide, a review round, a conversation. Keeping the original in `reference/` is what lets you check a rule that looks wrong and find out whether it was mis-derived or the source really does say that. Nothing reads this folder automatically, and that is deliberate. ## The `_shared` bank Alongside whichever bank is active, Supervertaler always loads a bank called **`_shared`**. It holds the defaults that are true of *your* work rather than of any one client: house style, domain conventions, jurisdictional rules. **Where they disagree, the active bank wins.** That is what a client bank is for – `_shared` says how you normally translate, and the client says how this one insists on it being done. The AI is told which layer is which, so it can apply the override rather than average the two. A rule earns its place in `_shared` once it has held across more than one client. Until then it stays in the bank where you found it, tagged in the Scope column. Promote by *moving* the row, not copying it, or the two drift apart. **Create `_shared` in the file system, not from the dropdown.** The name is reserved, and the *+ New memory bank…* dialog strips leading underscores from whatever you type – so asking it for `_shared` gets you an ordinary bank called `shared`, which does nothing. Instead use **Open folder**, go up one level to `memory-banks\`, create a folder called `_shared`, and put `brief.md`, `terminology.md` and `style.md` in it. You never have to select `_shared` to use it – it is loaded on top of whichever bank is active. Select it only when you want to edit your defaults. ## Banks ### Where they live ```plaintext D:\Supervertaler\memory-banks\ ├── _shared\ ← always loaded, alongside the active bank │ ├── brief.md │ ├── terminology.md │ └── style.md ├── acme-legal\ │ ├── brief.md │ ├── terminology.md │ ├── style.md │ └── reference\ └── pharma\ └── … ``` ### Switching The **Memory Bank** dropdown lists every bank it finds. Switching is immediate – the next chat turn and the next batch translation both use the new bank, no restart, and your chat history is preserved. The choice persists across Trados sessions. ### Creating Pick **+ New memory bank…** at the bottom of the dropdown, give it a short name (lowercase letters, digits, hyphens, underscores), and it is created with the three files already in place, each carrying its headings and a line explaining what belongs in it. ### Renaming and deleting Not yet available from inside the plugin. Close Trados and rename or delete the folder under `memory-banks\` directly. ## Filling a bank **Write in it.** Open the folder, edit `brief.md`, add rows to the table. This is the normal way, and there is no processing step between what you write and what the AI reads. **[Quick Add](/trados/ai-assistant/super-memory/quick-add/) (Ctrl+Alt+M)** captures a decision without leaving the segment you are on. It appends one row to `terminology.md`. **Drop source material into `reference/`** – a client style guide, a PDF, a glossary. Nothing happens to it automatically. When you want it in the bank, read it and write the parts that matter into the three files, or paste it into the chat and ask the assistant to draft the rows for you to check. That last point is the design in one line: **the AI proposes, you decide what gets written.** ## The Report button **☰ Report** tells you what the bank actually contributes: which files exist and how big, how many rows the terminology table has, **how many tokens get added to a prompt**, whether `_shared` is being applied, and warnings for things that are quietly wrong – a missing brief, a terminology file that is still prose rather than a table, files sitting in the bank root that are never sent to the AI. It reads the files directly, so it is instant and costs nothing. ## Converting a bank from the old layout Banks created before **v18.20.160** used a different structure: seven numbered folders and one file per fact. Those banks are **not read** by the current version – a bank with no `brief.md`, `terminology.md` or `style.md` contributes nothing to a prompt. You will not be left guessing: when the active bank is on the old layout, an amber **⚠ Convert this bank** button appears in the toolbar. Converting folds the old articles into the three files and moves the originals to `reference/_legacy`. **Nothing is deleted.** The conversion copies text across as-is; it does not tidy it up. Expect to read through the result and prune it – particularly the terminology, which arrives as prose and reads far better rewritten as a table. That work is yours on purpose: deciding which of a hundred old decisions still hold is judgement, and a machine that guesses confidently there is how the old system filled up with material nobody could check. ## Why this changed Earlier versions organised a bank as a self-organising wiki: seven folders, one Markdown article per fact, YAML metadata on each, and AI features (Process Inbox, Distill, Health Check) that filed and maintained it for you. It did not survive contact with real use. A single bank reached 136 terminology files – for what is a 136-row table – with a 97-file backlog nobody had processed. About 15% of articles had malformed metadata that silently excluded them from the very filtering the folders existed to enable: they were in the bank, and they were not reaching the AI. Nothing about that was visible from the outside, and by then the bank was far past the point where a human could read it and tell. The lesson was not that automation is bad, but that **knowledge you cannot audit is not knowledge you can rely on**. Three files can be read start to finish in a few minutes. If a rule in there is wrong, you will see it – which is the only mechanism by which it ever gets fixed. Process Inbox, Distill and Health Check are gone. They existed to manage complexity the new structure does not have. ## Working with a bank outside Trados The active bank is exposed over the [Supervertaler MCP server](/trados/mcp-server/), so Claude Desktop, Claude Code or any other MCP client can read it: `get_supermemory_context` for the current picture, `search_supermemory` to look a decision up, `list_supermemory_banks` to see what exists. Access is read-only. Beyond that, a bank is a folder of Markdown files. Edit it in any text editor, search it with ordinary tools, version-control it with Git, keep it in a synced folder so it follows you between machines. [Obsidian](https://obsidian.md/) works nicely if you like it, though with three files per bank you no longer need it to find your way around. Supervertaler Workbench does not use memory banks. That remains a genuine gap rather than a setting you have missed. ## Features | Feature | Description | | ----------------------------------------------------------------------- | ---------------------------------------------------------------- | | [**Quick Add**](/trados/ai-assistant/super-memory/quick-add/) | Capture a term decision while translating (Ctrl+Alt+M) | | [**Active Prompt**](/trados/ai-assistant/super-memory/active-prompt/) | Per-project prompt that Quick Add can also append terminology to | | [**AI Integration**](/trados/ai-assistant/super-memory/ai-integration/) | What gets sent to the AI, and in what order | | [**Obsidian Setup**](/trados/ai-assistant/super-memory/obsidian-setup/) | Optional: installing Obsidian and the Web Clipper | ## Related * [**Context layers**](/trados/context-layers/) – the full menu of context sources, with SuperMemory as one of them * [**AI Settings**](/trados/settings/ai-settings/) – toggles for enabling or disabling SuperMemory context # Active Prompt > Per-project prompt that Quick Add appends terminology to Each Trados project can have an **active prompt** – the prompt that Quick Add appends terminology to. This is also the prompt that is auto-selected in the [Batch Translate](/trados/batch-translate/) dropdown when you open the project. ## Setting the active prompt 1. Open **Settings → Prompts** 2. Right-click any prompt in the tree 3. Choose **Set as active prompt for this project** The active prompt is shown with a pin icon and bold blue text in the Prompt Manager, and a checkmark appears next to its name in the Batch Translate dropdown. The Batch Translate dropdown updates **live** – you do not have to close the Settings dialog for the change to take effect. Cancelling the dialog reverts the change; clicking OK persists it. To clear the active prompt, right-click it again and choose the same menu item (it toggles). ## See Also * [Quick Add](/trados/ai-assistant/super-memory/quick-add/) * [Batch Translate](/trados/batch-translate/) * [Prompts](/trados/settings/prompts/) * [Per-Project Settings](/trados/settings/project-settings/) # AI Integration > What SuperMemory sends to the AI, and in what order When you translate a segment, run a batch translation, or ask the chat a question, Supervertaler builds the prompt from several context sources. This page covers what SuperMemory contributes. ## What gets sent Two banks, in this order: 1. **`_shared`** – your house defaults, labelled as such. 2. **The active bank** – labelled as overriding the defaults above. Within each, the three files are sent whole: `brief.md`, then `terminology.md`, then `style.md`. There is no selection step and no filtering – whatever is in those files is what the AI sees. `reference/` is never sent. It holds the source material the three files were derived from, and a superseded draft answering as if it were current is precisely the failure it exists to prevent. ## Precedence The prompt states plainly that the client section overrides the house defaults. That instruction only works because the two layers are kept separate rather than merged, so the AI can tell which rule came from where. In practice: `_shared` might say *voorkeursvorm → preferred embodiment*, and a client bank might insist on *preferred form*. The client wins, and the override belongs in that client’s bank – not as an edit to `_shared`, which would change the default for everyone. ## The bank is the selection Earlier versions tried to work out which parts of a bank were relevant: matching your project name against client-profile filenames, detecting the document’s domain, preferring one style guide over another, then loading whichever articles scored highest. None of that happens now. **You pick the bank from the toolbar, and its contents are used** – because you already know which client you are working for, and a detection step could only get that wrong. It also means what reaches the AI is exactly what you would see by opening the folder, with nothing silently excluded. ## Token cost A bank is small enough to send whole. Three files for a single client typically come to a few thousand tokens. The **☰ Report** button tells you the exact figure for the active bank, including what `_shared` adds. Worth checking if you translate in large batches, where the context is re-sent for every call. If a bank does grow past the budget, the shared layer is dropped before the client layer – the client bank was chosen deliberately and overrides the defaults anyway – and terminology is dropped last on each, being the densest content and the hardest for a model to guess. ## How SuperMemory compares with other context sources SuperMemory does not replace your termbases or translation memories – it complements them, adding the reasoning that flat data cannot carry. | Context source | What it provides | What SuperMemory adds | | ----------------------------------------- | ----------------------------------- | ------------------------------------------------------------------------ | | **Termbases** (Supervertaler + MultiTerm) | Term pairs: A = B | The *why*: reasoning, rejected alternatives, client-specific overrides | | **Translation memories** | Previous wordings to anchor style | Rules that hold across segments, and which past work to trust | | **Document content** | What this document is | Conventions and pitfalls the AI cannot read off the page | | **AutoPrompt** | AI-drafted translation instructions | Client and domain context, so the draft starts from what you actually do | For when stacking all of them is or is not optimal, see **Stacking the layers** in [Context layers](/trados/context-layers/#stacking-the-layers). ## Memory-aware chat With SuperMemory context enabled, the chat can answer from your own decisions rather than from general knowledge: * “What register should I use for this client?” * “Does this client prefer *whilst* or *while*?” * “What’s the usual translation for *furtherance* here, and why?” If the bank does not cover it, the assistant falls back to general knowledge and says so. Because the banks are also readable over the [MCP server](/trados/mcp-server/), you can ask the same questions from Claude Desktop or Claude Code while Trados is open. ## Enabling and disabling Toggled in [AI Settings](/trados/settings/ai-settings/): * **Include memory bank in AI context** – for translations and chat. * **Use memory bank when generating prompts (AutoPrompt)** – when AutoPrompt drafts a translation prompt. Both are **off by default**. Turning them off does not delete anything – the files stay on disk. ## See Also * [SuperMemory](/trados/ai-assistant/super-memory/) – how a bank is structured * [Context layers](/trados/context-layers/) – the full menu of context sources * [AI Settings](/trados/settings/ai-settings/) – the toggles * [Batch Translate](/trados/batch-translate/) – batch translation with full context # Obsidian Setup > Setting up Obsidian for your memory banks Memory banks store all knowledge as Markdown files, which you can browse and edit with any text editor. For the best experience, we recommend [Obsidian](https://obsidian.md/) – a free knowledge-base app that visualises the links between your articles as an interactive graph. ## Installing Obsidian 1. Download Obsidian from (available for Windows, Mac, and Linux) 2. Install and open it – choose **Open folder as vault** and select one of your memory bank folders, for example: ```plaintext C:\Users\{you}\Supervertaler\memory-banks\default\ ``` If you keep several banks side by side, you can open each one as its own Obsidian vault and switch between them from Obsidian’s vault switcher. 3. The free version of Obsidian includes everything you need – no subscription required. (The paid Sync and Publish add-ons are not needed.) ## Web Clipper The [Obsidian Web Clipper](https://obsidian.md/clipper) is a free browser extension that lets you clip web pages straight into a memory bank’s `reference/` folder. Install it for Chrome, Firefox, Safari, or Edge. ### Setting up the Web Clipper 1. Install the extension from [obsidian.md/clipper](https://obsidian.md/clipper) 2. Make sure Obsidian is running with the memory bank you want to clip into open as a vault 3. Click the Web Clipper icon in your browser toolbar, then the gear icon (settings) 4. Create a new template (e.g. “memory-bank”) and set: * **Note location:** `reference` * **Vault:** select the memory bank vault you want clippings to land in 5. Optionally add properties: `source_url` = `{{url}}`, `clipped` = `{{date}}` Now when you find a useful reference – a client style guide, a terminology resource, a domain article – click the clipper, hit save, and it lands in that bank’s `reference/` folder. Nothing reads it automatically: `reference/` is source material, so when you want it in the bank, read it and write the parts that matter into `brief.md`, `terminology.md` or `style.md`. ## Recommended plugins These free Obsidian community plugins enhance the memory bank experience: * **Dataview** – query your vault like a database (e.g. list all terminology articles for a specific client) * **Calendar** – visualise when articles were created or modified * **Graph Analysis** – enhanced graph view with clustering and statistics To install plugins: **Settings → Community plugins → Browse**. ## See Also * [SuperMemory](/trados/ai-assistant/super-memory/) * [User Data Folder](/trados/data-folder/) # Quick Add (Ctrl+Alt+M) > Capture a term decision without leaving the segment You have just worked out how a term should be translated for this client. Quick Add records that decision without breaking your rhythm: it appends one row to the active bank’s `terminology.md` and puts you back in the segment. ## How to use 1. In the Trados editor, select the source text you want to capture. (Optional – the whole source segment is used if you select nothing.) 2. Press **Ctrl+Alt+M**, or right-click and choose **Add to SuperMemory**. 3. Fill in the dialogue: * **Source term** – pre-filled from your selection. The label names your project’s source language. * **Target term** – pre-filled from the target selection if you made one. * **Notes** – why, or when it applies. This is the part that will matter in six months. * **Save as raw note** – puts the text in `reference/` instead of the table, for when the decision is not settled enough to be a row. * **Also append to active translation prompt** – adds the same pair to the TERMINOLOGY table in your [active prompt](/trados/ai-assistant/super-memory/active-prompt/), so it takes effect on the very next Ctrl+T. 4. Click **Add**. The row lands in whichever bank is selected in the toolbar dropdown. To capture into a different bank, switch first. ## What gets written One row, appended to the table in `terminology.md`: ```markdown | fiche | plug | client | Only in the electrical sense; elsewhere "sheet" | ``` Successive additions accumulate in the same table rather than scattering, so the bank stays something you can read start to finish. The **Scope** column is filled in as `client`, which is the safe default – it means “true for this client”. If a decision later turns out to hold for other clients too, move the row to the `_shared` bank so every client gets it. Move rather than copy, or the two drift apart. ## Raw notes Tick **Save as raw note** and the text goes to the bank’s `reference/` folder instead, as a plain Markdown note. Use it when the knowledge is not yet a decision: *“fiche can mean either sheet or plug depending on context – check with the client”*. A table row states a rule, and a rule you are not sure about is worse than a note that says you are not sure. Nothing reads `reference/` automatically. When you have settled the question, write the row yourself. ## Review what you capture Quick Add writes what you type, with no AI step in between. That is the point – but it also means a typo in the target term becomes a rule the AI follows. Open `terminology.md` now and again (**📂 Open folder** in the toolbar) and read down the table. That is a two-minute job for a bank of a hundred rows, and it is the whole reason terminology is kept as a table rather than as a folder of files. ## Related * [**SuperMemory**](/trados/ai-assistant/super-memory/) – how a bank is structured * [**Active Prompt**](/trados/ai-assistant/super-memory/active-prompt/) – the prompt Quick Add can also append to * [**Keyboard Shortcuts**](/trados/keyboard-shortcuts/) – the full list # Supervertaler Bridge The **Supervertaler Bridge** is a small localhost-only HTTP service inside the Trados plugin. It is what the [Supervertaler MCP Server](/trados/mcp-server/) talks to: when Claude Desktop, Claude Code or another AI app reads your open project, searches a TM, runs a QA check or drafts translations into the document, every one of those calls goes over this bridge. It runs in the background, exposes its endpoints on `127.0.0.1` only, and is gated behind a per-session bearer token. You never need to configure it. This page exists so you know what is running, why it is safe, and where to look if the MCP server cannot find Trados. ## What it does The bridge exposes the state of the open Trados project to a local client, and accepts a small set of write actions from it: * The active source segment and your current target draft, with a few surrounding segments * TM matches Trados has found for the active segment, and concordance search over the project’s TMs * Termbase hits from your enabled termbases, and term lookups * Project name, file list, languages and statistics * Inserting or updating translations, adding comments, saving the document This is the same context the in-Trados Supervertaler Assistant chat uses for its own answers. The full list of operations is the MCP server’s [tool table](/trados/mcp-server/#what-it-can-do); the bridge is the plumbing under it. ## When it runs The bridge is started automatically when **both** of these are true: 1. You have **Assistant access** – a paid subscription or an active trial. Users without Assistant access never start the bridge. 2. You have **opened the Supervertaler Assistant panel** at least once in this Trados session. The panel is lazy – Trados doesn’t initialise it until you activate it. On start it writes a handshake file, `~/Supervertaler/trados/runtime/bridge.json`, holding the port, the token and the Trados process id; the MCP server reads that file to find the running Studio. The bridge is stopped when Trados Studio exits. If Trados crashes or is force-killed, the next start detects the stale handshake and replaces it with a fresh one. There is no switch to turn the bridge off. Until v18.20.188 a hidden `sidekickBridgeEnabled` setting existed for the retired Supervertaler Workbench integration; it was removed in v18.20.189, since the bridge now exists for the MCP server alone. A user without Assistant access never has a bridge running. ## Privacy and security The bridge is designed to be safe for everyday use: * **Loopback-only.** The HTTP listener binds exclusively to `127.0.0.1`. Other devices on your network – even on the same Wi-Fi – can never reach it. There is a defence-in-depth check that rejects any non-loopback `RemoteEndPoint` even if the binding ever drifts. * **Per-session authentication token.** A fresh GUID is generated every time the bridge starts. Clients must present it as a `Bearer` token. Stale tokens from previous sessions are useless. * **Random high port.** The bridge picks a random port in the 49152–65535 range to avoid collisions with other local services. * **No external network access.** The bridge only listens; it never reaches out to any external service. ## Troubleshooting The bridge writes a diagnostic log to two locations on every start: * `~/Supervertaler/trados/runtime/bridge.log` – under your Supervertaler user-data folder * `%TEMP%\Supervertaler-bridge.log` – guaranteed-writable fallback The log is truncated on every plugin start, so it always reflects the current Trados session. The first lines record the resolved data-folder path so you can see exactly where the plugin is looking. Useful entries to look for: | Log line | Meaning | | ---------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- | | `Initialize: HasAssistantAccess=false` | Your licence isn’t picked up as paid or trial. The bridge is correctly skipped in this case. | | `port NNNNN bind failed: HttpListenerException code=5` | Windows is refusing to let the plugin bind to a localhost port. Rare; usually means a strict group-policy environment. | | `Start() complete. Bridge live on http://127.0.0.1:NNNNN/` | All good – the bridge is running and the handshake file should be at `~/Supervertaler/trados/runtime/bridge.json`. | If `bridge.json` exists and contains `port`, `token`, `pid`, and `startedAt`, the bridge is healthy. The MCP server’s `list_trados_instances` tool shows every running Studio it can see. ## Endpoint reference (advanced) For developers who want to integrate other tools with the bridge, here are the two oldest endpoints; the MCP server’s tool definitions (`mcp-tools.json` in the plugin) describe the rest, each with its method, path and parameters. **The URL prefix is versioned** so future schema changes can ship without breaking older clients. ### `GET /v1/active-context` Returns a JSON snapshot of the current Trados project state. Authentication via `Authorization: Bearer ` from the handshake file. ```json { "available": true, "project": { "name": "ACME-PROJ-001", "fileName": "20260101 PROJ-001 Application as filed.docx", "sourceLang": "nl-BE", "targetLang": "en-US" }, "activeSegment": { "source": "...", "target": "..." }, "surroundingSegments": [ { "source": "...", "target": "..." } ], "tmMatches": [ { "score": 95, "source": "...", "target": "...", "tmName": "..." } ], "termbaseHits": [ { "source": "...", "target": "...", "termbaseName": "...", "definition": "...", "domain": "...", "notes": "..." } ] } ``` When no document is active, returns `{"available": false}` with HTTP 200. ### `POST /v1/insert-translation` Inserts text into the active Trados target segment via the same code path as the in-Chat Apply-To-Target button. Request body: ```json { "text": "The translation to insert" } ``` Response on success: ```json { "ok": true } ``` Response on failure (e.g. no active segment): ```json { "ok": false, "error": "no active document" } ``` ## Related pages * [Supervertaler MCP Server](/trados/mcp-server/) – the client this bridge exists for * [Supervertaler](/trados/ai-assistant/) – the in-Trados chat that uses the same context fields the bridge exposes * [User Data Folder](/trados/data-folder/) – where the handshake file lives # AI Cost Guide This page explains how AI costs work in Supervertaler for Trados and how to keep them under control. It deliberately avoids quoting exact per-model prices – those change often, and Supervertaler already shows you the **real, current cost** of every operation in the **Reports** tab. For exact figures, see [Estimates vs actual cost](#estimates-vs-actual-cost) below. ### Estimates vs actual cost The **Reports** tab shows **real billed token counts and cost** as reported by your provider’s API – with cache-hit tokens broken out (e.g. `830,000 in (720,000 cached) / 32,000 out · $1.36`). When the cost has no `~` prefix, that’s the actual amount your provider will charge. **This is the single best place to see what you’re actually spending** – it’s live, per-operation, and provider-reported. The number is cache-aware: * **Anthropic (Claude) native + OpenRouter → Claude**: real usage from `usage.input_tokens` + `cache_creation_input_tokens` + `cache_read_input_tokens`. Cache reads are billed at 0.1× the input rate, cache writes at 1.25×. * **OpenAI**: real `prompt_tokens` and `completion_tokens` plus `prompt_tokens_details.cached_tokens` for the auto-cache discount (50% off cached input). * **DeepSeek**: real `prompt_tokens` / `completion_tokens` with auto-cache (90% off cached input). * **Gemini 2.5+**: real `usageMetadata` with implicit cache (75% off cached input). For these providers the in-app number is the authoritative billable figure (modulo any account-level credits or monthly minimums you may have). The chars/4 estimate is still used as a fallback when the provider didn’t return usage info – this affects Ollama (local, free anyway), some provider edge cases, and any response shape we couldn’t parse. In those cases the cost still appears with a `~` prefix to flag it as an estimate. If you want to cross-check against your provider’s own dashboard: | Provider | Where to look | | ---------------------- | --------------------------------------------------------------------------------------- | | **Anthropic (Claude)** | [platform.claude.com – Cost](https://platform.claude.com/workspaces/default/cost) | | **OpenAI (GPT)** | [platform.openai.com – Usage](https://platform.openai.com/settings/organization/usage) | | **Google (Gemini)** | [console.cloud.google.com – Billing reports](https://console.cloud.google.com/billing/) | | **xAI (Grok)** | [console.x.ai – Usage](https://console.x.ai/team/default/usage) | | **Mistral AI** | [console.mistral.ai – Usage](https://console.mistral.ai/usage) | | **OpenRouter** | [openrouter.ai – Activity](https://openrouter.ai/activity) | | **DeepSeek** | [platform.deepseek.com – Usage](https://platform.deepseek.com/usage) | | **Ollama** | Free – local execution, no provider console. | The in-app number and the provider dashboard should agree to within rounding for any given run. If you see a meaningful gap, the most likely causes (in order) are: a provider-side credit or volume discount the in-app calculator can’t see; the in-app pricing table being a little behind a recent rate change; or, for fallback (estimate) cases, the chars/4 heuristic over- or under-counting tokens for that particular language and content type. ### How costs are calculated AI providers charge per **token** – a unit of text roughly equal to ¾ of a word. Costs depend on: * **Input tokens** – the text you send (source segment, system prompt, terminology context) * **Output tokens** – the text the model returns (translated segment, proofread text, generated prompt) Because Supervertaler translates **segment by segment**, the system prompt and terminology context are included with every segment. For a typical 5,000-word document (\~250 segments), the token usage works out roughly like this: | Task | Input tokens | Output tokens | | ------------------- | ------------ | ------------- | | **Batch Translate** | \~125,000 | \~8,000 | | **AI Proofreader** | \~140,000 | \~8,000 | | **AutoPrompt** | \~10,000 | \~2,000 | These are estimates for a representative document – actual usage varies with segment length, terminology context size, and prompt complexity. Token counts like these are fairly stable; what changes is the **price per token**, which is why this guide points you to live figures rather than quoting them. ### How much will it cost? There’s a wide spread between models. As a rough mental model: * **Local models (Ollama)** are **free** – they run on your own computer, with no API charges at all. The trade-off is that quality depends on your hardware, and they’re generally less capable than cloud-hosted models. If you have a computer with 8+ GB of RAM, TranslateGemma 12B delivers surprisingly good results for free. * **Budget cloud models** – the “Mini”, “Flash-Lite” and “Small” tier from each provider (e.g. GPT-5.4 Mini, Gemini 3.1 Flash-Lite, Mistral Small, Claude Haiku 4.5) – typically cost a small fraction of a cent per segment. They’re excellent for routine, high-volume translation. * **Flagship models** – Claude Opus 4.8, GPT-5.5, Gemini 3.1 Pro and the like – can run roughly 10–50× the price of the budget tier. Reserve them for specialised content where the quality difference earns its keep. To see what a model **actually** costs for your work, run one operation and check the **Reports** tab – it shows the real billed cost. For OpenRouter, expect the underlying provider’s rate plus a small platform fee. ### Our recommendation For budget-conscious batch work, **GPT-5.4 Mini** or **Gemini 3.1 Flash-Lite** offer excellent quality at a fraction of the price. For the absolute highest quality on specialised content, **Claude Opus 4.8** or **GPT-5.5** are worth the premium. ### Token pricing Supervertaler’s in-app cost figures come from a built-in per-token pricing table. Because provider prices change regularly, that table is occasionally a little behind a recent rate change – the **Reports** tab’s provider-reported figures are always the authoritative ones. For the definitive current rates, check the provider’s own pricing page: [OpenAI](https://openai.com/api/pricing/) · [Anthropic](https://www.anthropic.com/pricing#anthropic-api) · [Google Gemini](https://ai.google.dev/gemini-api/docs/pricing) · [xAI](https://docs.x.ai/developers/models) · [Mistral](https://mistral.ai/technology/) · [DeepSeek](https://api-docs.deepseek.com/quick_start/pricing/) · [OpenRouter](https://openrouter.ai/models) ### Tips for managing costs * **Start with a budget model** – GPT-5.4 Mini, Gemini 3.1 Flash-Lite, or Mistral Small are excellent for routine translation at a fraction of the cost of a flagship. * **Use premium models selectively** – reserve GPT-5.5, Claude Opus 4.8, or Gemini 2.5 Pro for specialised content (legal, medical, patents) where the quality difference justifies the cost. * **Try Ollama for zero cost** – if you have a computer with 8+ GB of RAM, TranslateGemma 12B delivers surprisingly good results for free. * **Check your usage** – the **Reports** tab lists every AI call live with its token count and cost; the **[Token Usage & Costs](/trados/usage-costs/)** report totals your spend over time (by project, client, model or month) and exports it to CSV/Excel; and your provider’s own console (see the [Estimates vs actual cost](#estimates-vs-actual-cost) table above) shows the authoritative billable figure. * **Set a monthly budget** – give Supervertaler a soft monthly limit (Settings → AI Settings) and it will warn you before a batch once you’ve reached it. See [Token Usage & Costs](/trados/usage-costs/#monthly-budget). ### Built-in cost protection Supervertaler includes several safeguards to help you avoid unexpected costs: #### QuickLauncher prompts are standalone When you run a prompt from the QuickLauncher menu (Alt+Q), only the prompt itself is sent to the AI – **not the chat history**. This means a simple terminology query costs only what it needs to, even if you have a long conversation in the chat window. #### Chat token budget Regular chat messages include recent conversation history so the AI can follow your discussion. However, Supervertaler automatically trims older messages when the history grows too large (\~50,000 tokens). This prevents costs from spiralling when previous messages contained large context blocks (e.g. full document content). #### Cost warning If a request is estimated to cost more than $0.50 in input tokens, a confirmation dialogue appears showing the estimated token count and cost. You can cancel before the expensive request is sent. ![]() #### Choosing the right model For everyday work – chat queries, terminology questions, QuickLauncher prompts – use **GPT-5.4 Mini** or another budget model. Reserve premium models like **GPT-5.5** or **Claude Opus 4.8** for AutoPrompt and complex tasks where the quality difference justifies the cost. ### See also * [Token Usage & Costs](/trados/usage-costs/) – the persistent usage log, the Usage & Costs report, CSV/Excel export, and the monthly budget * [AI Settings](/trados/settings/ai-settings/) – configure your API keys and choose a model * [Batch Translate](/trados/batch-translate/) – translate segments in bulk * [AI Proofreader](/trados/ai-proofreader/) – proofread translated segments * [AutoPrompt](/trados/generate-prompt/) – generate translation prompts * [Licensing & Pricing](/trados/licensing/) – Supervertaler subscription plans # Ai Proofreader The AI Proofreader checks your translated segments for errors using AI. It identifies issues such as mistranslations, omissions, grammar problems, and inconsistencies, and presents the results as clickable issue cards in the **Reports** tab. ## Starting a Proofreading Run 1. Open the **Supervertaler Assistant** panel (View > Supervertaler Assistant) 2. Switch to the **Batch Operations** tab 3. Select **Proofread** (instead of Translate) 4. Choose a **scope** from the dropdown 5. Optionally select a proofreading **prompt** from the prompt selector 6. Click **Proofread** ## Scope The scope dropdown controls which segments are checked: | Scope | Description | | ------------------------------------ | ------------------------------------------------------------------- | | **Translated only** | Checks only segments with Translated status | | **Translated + approved/signed-off** | Checks segments with Translated, Approved, or Signed-off status | | **All segments** | Checks every segment that has target text | | **Filtered segments** | Checks only segments visible after applying a Trados display filter | | **Filtered (translated only)** | Checks translated segments within the current filter | ## Prompt Selection When in Proofread mode, the prompt dropdown shows only prompts with the **Proofread** category. This keeps the list focused – translation prompts are hidden. If no prompt is selected, the AI uses a default proofreading instruction that checks for accuracy, completeness, grammar, and consistency. ### Default Proofreading Prompt The shipped **Default Proofreading Prompt** is deliberately slim. The hardcoded base of every Batch Proofread already includes the persona, the five quality categories (accuracy / completeness / terminology / grammar / number formatting), the output format, the “no full corrected translations” rule, and language-specific checks for Dutch, German, and French – so the prompt itself only needs to add what’s missing from the base. What the default prompt *does* add: * **Default to OK.** Raise an ISSUE only when a specific, demonstrable problem can be pointed to in the translation – never speculative or hypothetical concerns. * **Citation discipline.** When flagging a terminology consistency issue, the AI must cite specific source segment numbers in the **Evidence:** field – e.g. *“`'trekriem'` rendered as `'pull belt'` in `[SEGMENT 0031]`, `'draw strap'` in `[SEGMENT 0084]`”*. Inconsistency claims without concrete citations are not allowed. * **Source query distinction.** If the source itself contains an error (typo, duplication, missing word, internal inconsistency), the AI prefixes the Issue line with **“Source query:”** and notes whether the translation handled it correctly. A faithful rendering of a flawed source is not a translation error. * **Explicit boundaries.** The AI does not re-engineer the source, propose alternative terminology without a citation, flag stylistic preferences as errors, or flag empty target lines (those mean the segment hasn’t been translated yet). ## Reports Tab Proofreading results appear in the **Reports** tab of the Supervertaler Assistant panel. Each issue is shown as a clickable card containing: * **Segment number** – the actual per-file segment number as shown in the Trados editor grid * **Issue description** – what the AI found wrong * **Evidence** *(when applicable)* – specific source segment numbers the AI cites to back up the claim, shown in italic grey between the issue and the suggestion. Required for terminology consistency claims (see *Default Proofreading Prompt* below) so you can verify the inconsistency yourself by jumping to the cited segments. * **Suggestion** – the AI’s recommended fix (if available) Right-click any card to copy the issue, the evidence, the suggestion, or the whole card to the clipboard. ### Navigating to Issues Click any issue card to navigate directly to that segment in the Trados editor. This works correctly in multi-file projects – the plugin uses the segment’s internal identifiers to find the exact segment. ### Dismissing Issues Each issue card has a checkbox. Tick it to dismiss the issue and remove it from the list. This lets you work through the results one by one, keeping track of which issues you have already addressed. When all issues have been dismissed, the Reports tab shows “All issues addressed – well done!” ### Saving the report (from v18.20.187) Every completed proofreading run is written to disk automatically, as a Markdown file in `trados\ eports` inside your Supervertaler data folder – one section per segment with the issue, suggestion, evidence, source and target. The footer of the Reports tab names the file (hover it for the full path), and the Batch Operations log shows the path too. So a report that has been cleared, or lost when Studio refreshes the panel, is never gone. To keep a copy somewhere else – a client folder, an email attachment – click **Save report…** next to **Clear**. It writes the same Markdown to a location of your choice, and it is only enabled while a proofreading report is showing. ### The report stays until you are finished (from v18.20.187) The report also stays in the Reports tab until you clear it. Close Studio and reopen the document, or switch to another document and back, and the report is put back as you left it: the issues you had ticked off stay ticked off, and clicking a card still takes you to the segment. A report is only ever restored for the document it was made on. Press **Clear** when you are done with it. ### Clearing Results Click the **Clear** button at the top of the Reports tab to remove all results and start fresh. The automatic copy on disk is unaffected. ### Run Summary After a proofreading run, the Reports tab shows: * Total number of issues found and segments checked * Run timestamp and duration in the footer ## Adding Issues as Trados Comments Check the **“Also add issues as Trados comments”** checkbox in the Batch Operations tab (visible only in Proofread mode) before starting the run. When enabled, each issue found by the proofreader is also inserted as a Trados segment comment, so you can see the issues directly in the editor without switching to the Reports tab. ## AI Context in Proofreading Batch Proofread builds a richer context than Batch Translate – it has to, because verifying whether a term is rendered consistently across the document is exactly the kind of question the AI needs the whole document to answer. * **Full bilingual document context** – when **Include document context** is enabled in [AI Settings](/trados/settings/ai-settings/), every segment in the document is included with both source AND target text, with no truncation. This is what makes target-side consistency verifiable: the AI can check “this term is rendered as X in \[SEGMENT 0031] and Y in \[SEGMENT 0084]” against the actual document, not against a guess. Segment numbers in the document context match the `[SEGMENT XXXX]` numbers the AI sees in the batch it’s reviewing, so citations cross-reference both ways. * **Termbase terms** – terminology from enabled termbases is checked against the translations, including term definitions and domains when that option is enabled. Forbidden terms are flagged with a `⚠️ DO NOT USE` marker so the AI knows to flag them as issues if it sees them in the translation. * **Language-specific checks** – Dutch, German, and French targets get auto-included quality checks (compound spelling, dt-errors, de/het articles for Dutch; capitalisation and case system for German; accents and punctuation spacing for French). These come from the hardcoded base and don’t need to be in your custom prompt. * **Custom prompts** – the selected proofreading prompt provides domain-specific quality checks on top of all of the above. TM matches and surrounding segments are **not** included in proofreading – these are Chat & QuickLauncher features only. See the [AI Settings](/trados/settings/ai-settings/) page for a full comparison table. Caution **Token cost:** Sending the full bilingual document roughly doubles the context size compared to source-only. For typical patent / legal / technical jobs (under \~500 segments) this is a minor cost increase – usually a few extra cents per batch on Sonnet-class models. For very long documents the cost scales linearly; if you proofread a 5,000-segment book you may want to disable Include document context and rely on per-batch context only. ## Clipboard Mode If you prefer to use a web-based AI (ChatGPT, Claude, Gemini, etc.) instead of an API, tick the **Clipboard Mode** checkbox. Supervertaler builds a complete proofreading prompt with both source and target text for each segment and copies it to your clipboard. See [Clipboard Mode](/trados/clipboard-mode/) for full details. ## Tips ### Start with Confirmed Segments Use the **Confirmed Only** scope to check segments you consider finished. This avoids noise from segments that are still being worked on. ### Use Domain-Specific Proofreading Prompts Create custom proofreading prompts tailored to your domain. For example, a medical proofreading prompt can check for correct use of clinical terminology, while a legal proofreading prompt can verify that defined terms are used consistently. ### Review After AI Translation The AI Proofreader pairs well with [Batch Translate](/trados/batch-translate/). After translating a batch of segments with AI, run the proofreader to catch any issues before final review. ### Combine with Display Filters Use Trados display filters to isolate specific segments (e.g., segments containing a certain term), then proofread only those filtered segments for targeted quality checks. *** ## See Also * [Clipboard Mode](/trados/clipboard-mode/) * [Batch Translate](/trados/batch-translate/) * [Prompts](/trados/settings/prompts/) * [Supervertaler](/trados/ai-assistant/) * [Keyboard Shortcuts](/trados/keyboard-shortcuts/) # AutoTagger AutoTagger looks at where the inline tags sit in the **source** segment and inserts that same set of tags into your **existing translation** at the right places – without changing any of the translated words. It is for the common case where a target has the correct translation but is **missing its tags or has them in the wrong spots** – typically after machine translation, pasting from another tool, or typing the target by hand. In Trados Studio those segments otherwise trip the tag QA checks even though the wording is fine. ## How to use it With an active segment that has a correct translation but wrong/missing tags: * Right-click in the editor → **Auto-tag active segment**, or * Press **Ctrl+Alt+G**.  Trados Undo (`Ctrl+Z`) reverts it. AutoTagger works **without opening the Supervertaler Assistant pane**, and it never opens that pane – it reads the active segment from the editor and its settings from disk, so it just works without disturbing your layout, even straight after a Trados restart. ## How it works 1. AutoTagger reads the source segment’s inline tags and your current target text. 2. It asks the AI to place that exact set of tags into your translation at the correct positions. 3. It **validates** the result before writing: the tag set must match the source, the words must be unchanged, and the tags must be well-formed. 4. It re-inserts the tags into your **exact** target, so punctuation such as curly quotes is preserved verbatim. 5. If the AI’s output doesn’t validate it **retries once**, and otherwise leaves the segment **untouched** – so it never writes broken tags. AutoTagger reuses the same tag engine as Batch Translate, so the tags it writes are real Trados inline tags, not placeholders. ## Configuring it Settings → **Prompts** → **AutoTagger Instruction**. This editable field tells the AI how to place the tags. It supports these placeholders: | Placeholder | Meaning | | ----------------- | ---------------------------------------- | | `{{SOURCE_TEXT}}` | The source segment, with its inline tags | | `{{TARGET_TEXT}}` | Your current translation (tags stripped) | | `{{TAG_LIST}}` | The list of tags that must be placed | ## Tracking cost AutoTagger’s AI calls are logged under their own **“AutoTagger”** task in [Token Usage & Costs](/trados/usage-costs/), with token counts and cost like every other AI call. ## Notes * **v1 is single-segment.** A batch mode may follow. * **Shortcut:** Ctrl+Alt+G triggers AutoTagger. The floating TermLens popup opens with **Alt+L**; you can reassign it in Trados’ keyboard settings if you like. * AutoTagger mirrors the [AutoTagger feature in Supervertaler Workbench](/workbench/ai-translation/autotagger/). *** ## See Also * [Batch Translate](/trados/batch-translate/) * [Import/Export](/trados/import-export/) * [Token Usage & Costs](/trados/usage-costs/) * [Keyboard Shortcuts (Trados)](/trados/keyboard-shortcuts/) # Batch Operations The **Batch Operations** tab in the Supervertaler Assistant panel provides two AI-powered modes for processing multiple segments at once: | Mode | Description | | ----------------------------------------------- | ---------------------------------------------------------------- | | **[Batch Translate](/trados/batch-translate/)** | Translate segments using AI with customisable prompts | | **[AI Proofreader](/trados/ai-proofreader/)** | Check translations for errors, inconsistencies, and style issues | Switch between modes using the **Mode** dropdown at the top of the Batch Operations tab. Both modes share the same prompt selector, provider/model configuration, and scope options. Prompts are filtered by mode – Translate prompts appear in Translate mode, Proofread prompts appear in Proofread mode. You can click the **provider/model label** to quickly switch AI models via a flyout menu – the same menu available in the Chat tab. ### Clipboard Mode Both Translate and Proofread modes support **[Clipboard Mode](/trados/clipboard-mode/)** – an alternative workflow that lets you use any web-based AI (ChatGPT, Claude, Gemini, etc.) without an API key. Tick the **Clipboard Mode** checkbox to switch from API-based processing to a manual copy/paste workflow. See [Clipboard Mode](/trados/clipboard-mode/) for full details. ### Preview prompt Next to the action button, the **👁 Preview prompt** link opens a read-only dialog showing **exactly what would be sent to the AI** for the current configuration: the assembled system prompt (including the active custom prompt, termbase entries, language-specific checks, and the full bilingual document context for proofread), followed by the numbered segment list. No LLM call is made. This is useful for: * **Sanity-checking before an expensive call** – see what the model will actually receive (including how many tokens of context, whether your termbase is being included, whether the right segments are in scope) before clicking Translate / Proofread. * **Debugging unexpected output** – if the AI produces an odd suggestion, the preview shows you the exact prompt the model was answering, so you can see whether the issue is in your custom prompt, the termbase, the document context, or the segment list. * **Manually pasting into a web LLM** – the dialog has its own *Copy to clipboard* button, so you can use it as a one-shot “send this to ChatGPT/Claude/Gemini” path without toggling Clipboard Mode. The preview works in both **API mode** and **Clipboard Mode** without switching, and is available for both Translate and Proofread. ### SuperBench Next to Preview prompt, the **⚖ SuperBench…** link (from v18.20.187) translates the first segments of the document with three models under exactly these batch settings and has a judge compare them blind, with a recommendation for this project. Nothing is written to the document. See [SuperBench](/trados/superbench/). ### List numbering as structure context Word’s claim numbers, lettered steps and bullets are not segment text, so the AI used to never see them. Since v18.20.188 (always on from v18.20.189; see [AI Settings](/trados/settings/ai-settings/#list-numbering-as-structure-context-from-v1820188-always-on-from-v1820189)), Batch Translate prefixes the first segment of each numbered paragraph with its marker inside a sentinel – `[#e)]`, `[#9.]` – and tells the model it is structure, never to be reproduced. The log reports how many markers were found, and any marker the model echoes back is removed before the target is written. Preview prompt shows the markers as they will be sent. ### Reference numbers Technical documents – patents, manuals, specifications – point at parts of a drawing with numbers in brackets: “the valve (12) is connected to the pipe (3a)”. The **Reference numbers - like “(12)”** link lists every such number in the open document, how often it is used, and the sentence that first mentions it. It also names any number the sequence skips – a document citing (1) to (4), (6) and (7) is told that (5) is cited nowhere, which usually means a part was renumbered or dropped while the document was drafted. It reads the whole document regardless of the Scope setting, makes no AI call, and opens the list in the Chat tab. A document without such numbers simply says so. Useful for spotting a number that is cited once and never explained, or a part that changes number halfway through. ### FigureLens (from v18.20.189) The AI sees the text of your documents, not the pictures in them. **FigureLens** fixes that in two steps, and it tells you at each step what will happen and what it costs. The **FigureLens…** link opens it.  Click 1: the **FigureLens…** link, under Batch Operations.  Clicks 2 and 3, in the panel that opens: **Extract images to a folder** (free, no AI), then **Describe images with AI** – one AI request per image. **Describe from the text only** is the free alternative to that second button, not a third step.  What is in the document: a picture the AI cannot see.  What Step 2 writes: the description the AI reads with every request. **Your documents** – a summary line and a two-column table of every Word document in the project, name in one column and what was found in it in the other (the source-language files in Studio’s Files view; reference files are skipped): how many images each holds and how many carry a figure label, the documents with images first, then those with none in grey, then any that could not be read in red. Nothing outside the project is scanned; if the pictures are in a separate document, add it to the project. **Step 1 – Extract images to a folder…** The first time, it asks where to put the images; a new, empty folder next to the job is fine, and the choice is remembered for this project. Then it copies the images out of the documents into that folder, named after their figure numbers (`Figure 01.png`, `Figure 02.png`…). If more than one document has images, each gets its own sub-folder inside it, so two documents’ `Figure 01` cannot overwrite each other. Drawings held as vector images (EMF or WMF, which is what a drawing placed from CAD usually is) are rendered to PNG on the way out, because no AI can read a metafile. Free, no AI. If you already keep the images in a folder of your own, use **Already have the images in a folder? Choose it…** instead, and later **Change…** to switch folder or **Open folder** to look at them. **Step 2 – Describe images with AI.** Shows each image to the AI together with what the document says about it, and saves a description of each – what it shows, which figure it is, which parts and numbers appear in it – as `figures.md` in the active memory bank. That file is read by the AI with every request from then on, so it knows what your images mean in this document. Each document gets its own table in the file. One AI request per image; the button says how many and to which provider before you click. It asks before replacing descriptions that already exist. **Describe from the text only** is the free alternative: only what the document itself says about each figure, without looking at the images. Use one or the other. **Result** – whether the descriptions exist yet, when they were saved, how many figures, and whether they came from the AI or from the text alone. The descriptions are saved in the active memory bank, and that must be a bank of this project’s own: the shared bank is read by every project, so the panel refuses to write there and instead offers **Create memory bank “” for this project and switch to it**, one click. If you already keep a bank for the project, pick it on the Chat tab first. Buttons that cannot run yet say why: no images in the documents, step 1 not done, or no active memory bank. The **Document images report** link at the bottom opens the full per-image listing in the Chat tab. **Reference numbers** stays a separate link above, because it is a check on the text, not part of this pipeline. ### AutoPrompt The Batch Operations tab also includes an **[AutoPrompt](/trados/generate-prompt/)** link that uses AI to create a comprehensive, domain-specific translation prompt based on your project’s content, terminology, and TM data. ## See Also * [Clipboard Mode](/trados/clipboard-mode/) * [SuperBench](/trados/superbench/) * [AutoPrompt](/trados/generate-prompt/) * [Prompts](/trados/settings/prompts/) * [AI Settings](/trados/settings/ai-settings/) * [Keyboard Shortcuts](/trados/keyboard-shortcuts/) # Batch Translate Batch Translate lets you translate multiple segments at once using AI. It is located in the **Supervertaler Assistant** panel, on the **Batch Operations** tab. ![]() ### Starting a Batch Translation 1. Open the **Supervertaler Assistant** panel (View > Supervertaler Assistant) 2. Switch to the **Batch Translate** tab 3. Choose a **scope** from the dropdown 4. Choose a **prompt** from the prompt selector 5. Click **Translate** ### Scope The scope dropdown controls which segments are translated: | Scope | Description | | --------------------------- | -------------------------------------------------------------------------------------------------------------- | | **Empty Segments Only** | Translates segments that have no target text | | **All Segments** | Translates every segment in the file | | **All unfinished segments** | Translates every segment that isn’t Translated, Approved or Signed off – drafts and rejected segments included | | **Filtered Segments** | Translates only the segments currently visible after applying a filter | | **Filtered Empty Only** | Translates empty segments within the current filter | ### Prompt Selection Choose a prompt to guide the AI translation style and domain. The prompt selector shows: * **Default Translation Prompt** – a general-purpose prompt that works well for most content types. Use it as-is or duplicate it in the Prompt Manager and customise it for your domain. * **Custom prompts** – your own prompts created in the Prompt Manager The **active prompt** for the current project is marked with a checkmark in the dropdown. When you open a project that has an active prompt set, it is automatically selected. See [Memory banks – Active Prompt](/trados/ai-assistant/super-memory/active-prompt/) for how to set the active prompt. ### Provider and Model The current AI provider and model are displayed below the prompt selector. Click the provider/model label to open a flyout menu where you can switch models instantly – the same menu available in the Chat tab. Alternatively, open the settings dialogue (gear icon in the TermLens header) and go to the **AI Settings** tab. Your **custom OpenAI-compatible profiles** (institutional gateways, self-hosted endpoints) appear at the bottom of the same menu under *Custom (OpenAI-compatible)*, each showing its configured model, with the active profile ticked – so switching between custom endpoints is one click, no trip to Settings. *(From v18.20.154.)* ### Progress and Logging During translation: * A **progress bar** shows overall completion * A **real-time log** displays the status of each segment as it is translated * The **Stop** button aborts the batch at any time – segments already translated are kept ### Translate Active Segment (Alt+T) Press **Alt+T** to translate the active segment instantly. This uses the same provider, model, and prompt as Batch Translate, so you can switch prompts or providers and immediately use them for single segments with Alt+T. Alt+T is also available via right-click in the editor (“Translate active segment”). #### How it works 1. The active segment’s source text is sent to the AI provider configured in AI Settings 2. The selected prompt (from the Batch Translate tab) is applied, along with termbase terms 3. The same document context and SuperMemory context as a batch run is included *(from v18/19.20.149 – earlier versions sent the segment on its own, which is why single segments used to translate noticeably worse than a batch)* 4. The translation is written directly into the target cell 5. Inline tags (bold, italic, field codes, etc.) are preserved in the translation In short: a single segment now gets everything a batch run gets, minus the other segments – same prompt, same terminology, same document context. On versions before 18/19.20.149, batch translating even small ranges gave better results than going segment by segment; from 18/19.20.149 the two are equivalent. ### AI Context in Batch Translate Batch Translate uses several context sources from your [AI Settings](/trados/settings/ai-settings/) to improve translation quality: * **Document content** – when enabled, all source segments are included in the system prompt so the AI can determine the document type (legal, medical, technical, etc.) and adapt its style accordingly. This is shared across all batches. * **Termbase terms** – terminology from enabled termbases is injected into the prompt, including term definitions and domains when that option is enabled. * **Custom prompts** – the selected prompt provides domain-specific translation instructions. TM matches and surrounding segments are **not** included in Batch Translate – these are Chat & QuickLauncher features only. See the [AI Settings](/trados/settings/ai-settings/) page for a full comparison table. ### Backup TMX The **Auto-backup translations to TMX** checkbox is ticked by default. When enabled, Supervertaler writes every translated segment to a TMX file as it arrives from the AI. If Trados crashes mid-run, you can recover the completed translations without re-running the batch. The TMX files are also useful outside of crash recovery – you can import them into any TM in Trados, memoQ, Wordfast, or any other CAT tool that accepts standard TMX. Click **Open folder…** next to the checkbox to open the backup folder directly in Windows Explorer. To disable backups for a particular run, simply untick the checkbox before clicking Translate. #### How it works * A new `.tmx` file is created at the start of each batch run. * Every **10 translated segments**, the file is rewritten in full – so at most 10 segments are lost in a crash. * The file is written atomically (via a temp file + rename) so it is always a valid, complete TMX – never a partial or corrupt file. * At the end of a completed or cancelled run, the file is flushed one final time. #### Where the files are saved ```plaintext C:\Users\\Supervertaler\trados\batch_backups\ ``` Files are named by timestamp and project name, for example: ```plaintext batch_2026-04-10_14-23-01_YAXINCHENG.tmx ``` The exact path is also printed to the **Batch Translate log** at the start of each run. #### Recovering after a crash 1. Reopen Trados Studio and your project. 2. Open your TM in **Trados Translation Memories** (or via the project’s TM settings). 3. Use **Import** → browse to the backup `.tmx` file → import. 4. Run **Pre-translate** on your project to apply the recovered translations from the TM. ### Clipboard Mode If you prefer to use a web-based AI (ChatGPT, Claude, Gemini, etc.) instead of an API, tick the **Clipboard Mode** checkbox. This replaces the Provider and Translate button with **Copy to Clipboard** and **Paste from Clipboard** buttons. Supervertaler builds a complete, ready-to-use prompt – including your selected prompt, terminology, document context, and numbered bilingual segments – and copies it to your clipboard. See [Clipboard Mode](/trados/clipboard-mode/) for full details. ### Tips #### Translate Empty Segments First Start by translating only the empty segments (scope: **Empty Segments Only**). Review the results, then fix any issues. This avoids overwriting segments you have already edited. #### Generate a Domain-Specific Prompt Automatically Click **AutoPrompt…** next to the prompt dropdown. Supervertaler analyses your entire document, detects the domain, and uses AI to generate a comprehensive translation prompt with terminology rules, style guidelines, and anti-truncation controls – all tailored to your specific project. See [AutoPrompt](/trados/generate-prompt/) for details. #### Create Domain-Specific Prompts Manually For specialised content, you can also duplicate the Default Translation Prompt in the Prompt Manager and add domain-specific instructions (terminology rules, style preferences, formatting requirements). A tailored prompt is the single most effective way to improve translation quality. #### Combine with TM If your project has a translation memory, TM matches are shown alongside AI translations. You can pre-translate with TM first (using Trados’s built-in batch tasks), then use Batch Translate to fill in the remaining empty segments with AI. #### Review After Batch AI translation is a first draft. After a batch run: 1. Review each translated segment 2. Fix any terminology or style issues 3. Confirm segments with **Ctrl+Enter** (Trados default) *** ### See Also * [Clipboard Mode](/trados/clipboard-mode/) * [AutoPrompt](/trados/generate-prompt/) * [AI Proofreader](/trados/ai-proofreader/) * [Supervertaler](/trados/ai-assistant/) * [TermLens](/trados/termlens/) * [SuperMemory](/trados/ai-assistant/super-memory/) * [Keyboard Shortcuts](/trados/keyboard-shortcuts/) # Clipboard Mode Clipboard Mode lets you translate or proofread segments using **any web-based AI** – ChatGPT, Claude, Gemini, DeepSeek, or any other LLM with a chat interface – without needing an API key. Instead of sending segments to an AI provider via API, Supervertaler builds a ready-to-use prompt and copies it to your clipboard. You paste it into the AI of your choice, copy the response, and paste it back. Clipboard Mode is also ideal if you want to use a model that is not available via API, if you prefer a pay-as-you-go chat subscription, or if you want to try different AI models before committing to a specific provider’s API. ## How It Works Clipboard Mode is available in both **Translate** and **Proofread** modes on the Batch Operations tab. ### Translating with Clipboard Mode 1. Open the **Supervertaler Assistant** panel and switch to the **Batch Operations** tab 2. Set the mode to **Translate** 3. Tick the **Clipboard Mode** checkbox 4. Choose a **scope** (Empty Segments Only, All Segments, etc.) 5. Optionally select a **prompt** to customise the translation instructions 6. Click **Copy to Clipboard** 7. Open your preferred web-based AI (ChatGPT, Claude, Gemini, etc.) 8. Paste the prompt into the chat and send it 9. Copy the AI’s full response 10. Switch back to Trados and click **Paste from Clipboard** The translations are written into the target segments automatically, with full tag reconstruction and validation. ### Proofreading with Clipboard Mode 1. Set the mode to **Proofread** and tick **Clipboard Mode** 2. Click **Copy to Clipboard** – the prompt includes both source and target text for each segment 3. Paste into your AI, copy the response, and click **Paste from Clipboard** ## What Gets Copied When you click **Copy to Clipboard**, Supervertaler builds a comprehensive prompt that includes: * **System instructions** – the same translation or proofreading instructions used by the API-based batch modes * **Custom prompt** – your selected prompt from the Prompt Manager, if any * **Terminology** – terms from your enabled termbases, including definitions and domains (when term metadata is enabled in AI Settings) * **Document context** – source segments from the document (when enabled in AI Settings), so the AI understands the document type and domain * **Numbered bilingual segments** – each segment is numbered and formatted with status annotations This is not just a list of segments – it is a fully self-contained prompt ready to paste into any LLM chat window. ### Segment Format Each segment is formatted as a numbered bilingual block: ```plaintext Segment 1 [new]: Dutch: Polyvision breidt de mogelijkheden uit. English: Segment 2 [fuzzy, 85%]: Dutch: Nieuwe toepassingen in onderwijs. English: New applications in education. Segment 3 [translated, 100%]: Dutch: Doelstelling lange termijn. English: Long-term objective. ``` The per-segment labels use short language names (e.g. “Dutch”, “English”) to save tokens. The full language names with regional variants (e.g. “Dutch (Netherlands)”, “English (United Kingdom)”) are stated once in the system prompt at the top. ### Status Annotations Each segment header includes a status annotation in square brackets: | Status | Meaning | | ------------------------- | ---------------------------------------- | | **\[new]** | No target text – needs translation | | **\[fuzzy, N%]** | TM fuzzy match at N% – may need revision | | **\[translated, 100%]** | 100% TM match – likely correct | | **\[translated]** | Human-edited translation | | **\[machine translated]** | Machine translation output | | **\[draft]** | Has target text but origin is unclear | These annotations help the AI understand the state of each segment and respond appropriately – for example, a fuzzy match may only need minor adjustments rather than a full retranslation. ## Tag Handling Inline tags (bold, italic, hyperlinks, field codes, etc.) are serialised as numbered placeholders before being sent to the AI: | Tag type | Placeholder | | ---------------- | ---------------------- | | Opening tag | ``, ``, etc. | | Closing tag | ``, ``, etc. | | Self-closing tag | ``, ``, etc. | For example, a segment like “Click **here** for details” becomes: ```plaintext Click here for details ``` The AI is instructed to preserve these placeholders exactly as they appear. When you paste the response back, Supervertaler reconstructs the original Trados tags from the placeholders – the same tag reconstruction pipeline used by API-based Batch Translate. Caution If a tag is missing or malformed in the AI’s response, Supervertaler reports a warning but still writes the translation. Check the log for any tag validation messages. ## Choosing an AI Model Any web-based LLM with a chat interface works with Clipboard Mode. Some recommendations: * **Claude** (claude.ai) – excellent at following the bilingual format precisely and preserving tags * **ChatGPT** (chatgpt.com) – widely available, works well with the structured format * **Gemini** (gemini.google.com) – large context window, good for bigger batches * **DeepSeek** (chat.deepseek.com) – strong multilingual capabilities For best results, use the most capable model available in your subscription (e.g., Claude Opus, GPT-4o, Gemini Pro). ## Clipboard Mode vs API Mode | | Clipboard Mode | API Mode | | -------------------- | ---------------------------------------------- | -------------------------------------------- | | **API key required** | No | Yes | | **Setup time** | None – works immediately | Requires provider account and API key | | **Cost** | Included in your AI chat subscription | Pay-per-token via API | | **Automation** | Manual copy/paste | Fully automatic | | **Model choice** | Any web-based LLM | OpenAI, Anthropic, Google, Ollama | | **Best for** | Getting started, quick jobs, trying new models | Large projects, automation, batch processing | Both modes use the same prompts, terminology, document context, and tag handling – the only difference is how the text gets to and from the AI. ## Combining with AutoPrompt – the hybrid pattern [AutoPrompt](/trados/generate-prompt/) **always uses your configured AI provider** to generate the meta-prompt – Clipboard Mode does **not** apply to AutoPrompt, only to the actual Translate / Proofread passes. This is intentional, and it enables a useful hybrid workflow: 1. Tick **Clipboard Mode**. 2. Click **AutoPrompt…** – the prompt-generation request still goes through your configured API (a small, one-shot call, even on an Opus-class model this is cheap relative to bulk translation). 3. Refine the generated prompt in the AI Assistant chat and **Save as Prompt…**. 4. Select the saved prompt from the dropdown. 5. Click **Copy to Clipboard** – Supervertaler builds a ready-to-paste batch for your web-based AI using the AutoPrompt-generated system prompt. 6. Paste into ChatGPT / Claude.ai / Gemini, copy the response, click **Paste from Clipboard**. The result: paid API for the small-but-clever prompt-writing call, free web tier for the expensive bulk translation. You get the full AutoPrompt analysis pipeline (TermScan, domain detection, sampling of confirmed reference pairs) without paying per-token API rates for the bulk Translate. ## Tips ### Use the Best Model Available Since you are not paying per token in Clipboard Mode, there is no cost difference between models. Use the most capable model your subscription offers. ### Check the Response Format Before clicking Paste from Clipboard, glance at the AI’s response to make sure it followed the numbered bilingual format. Most modern LLMs handle this correctly, but if the format is off, you can ask the AI to reformat its response. ### Combine with Terminology Clipboard Mode includes your termbase terms in the prompt, just like API mode. Make sure your termbases are set up and enabled in AI Settings for the best results. ### Name Prompts After Your Projects If you save a custom prompt with the same name as your Trados project (e.g. “HAYNESPRO” for a project called HAYNESPRO), the prompt dropdown will auto-select it whenever you open that project. This works for both Translate and Proofread modes and saves you from having to reselect the correct prompt each time. ### Process in Batches For large documents, use the scope dropdown to work through segments in manageable batches – for example, use display filters to select a section at a time, then use the **Filtered Segments** scope. *** ## See Also * [Batch Translate](/trados/batch-translate/) * [AI Proofreader](/trados/ai-proofreader/) * [Batch Operations](/trados/batch-operations/) * [AI Settings](/trados/settings/ai-settings/) * [Prompts](/trados/settings/prompts/) # Context layers > The ten layers of context Supervertaler for Trados puts in front of the AI, what each one adds, and how to control them. A translation engine that sees only the sentence in front of it will translate that sentence well and the document badly. Supervertaler’s design is the opposite: every time you send a chat message, translate a batch of segments, or ask AutoPrompt to draft a prompt, it assembles a fresh snapshot of your work and hands the whole thing to the AI. That snapshot is built in **layers**. Some come from Trados, some from your own knowledge, and two of them come from parts of the document that no CAT tool normally shows you at all. They stack, and each one that is present removes a class of mistake the AI would otherwise make. This page is the single place that lists every layer. Each section is a short overview with a link to the feature’s own page. ## The ten layers | # | Layer | Where it comes from | On by default | | -- | ---------------------------- | --------------------------------------- | ------------------------------ | | 1 | Project and file information | Trados | always | | 2 | Current segment | Trados | always | | 3 | Surrounding segments | Trados | always | | 4 | Full document content | Trados | yes | | 5 | A translation memory match | your TMs | yes | | 6 | Termbase terms | your termbases | yes | | 7 | SuperMemory | what you have recorded about the client | yes, when a bank is active | | 8 | List numbering | the Word file inside the sdlxliff | yes, from v18.20.189 | | 9 | Figure descriptions | the images in your documents | after two clicks in FigureLens | | 10 | Attached files | you, per chat turn | when you attach something | Layers 1 to 8 need no work from you at all (layer 5 only where Studio has already put a TM hit in the segment). Layer 9 is two clicks per project. Layer 10 is deliberate. ### 1. Project and file information Which project and file you are in, the language pair (e.g. Dutch → English), and your position in the document (“Segment 42 of 318”). Always included; no toggle. ### 2. Current segment The source text you are translating and any target you have already entered. Always included – the minimum context for most AI operations. ### 3. Surrounding segments Two segments before and two after, with their translations where available. This is what lets the AI resolve a pronoun the way the previous sentence resolved it, or continue a clause that began in the segment above. Always included; the window is fixed. ### 4. Full document content All source segments in the current document, so the assistant can judge what kind of document it is – legal, medical, technical, marketing, financial, scientific – and let that inform its terminology and register. Very long documents are truncated to a configured maximum (default 500 segments), keeping the first 80 % and the last 20 % so the beginning and the end both survive. **Toggle:** AI Settings → *Include full document content*. ### 5. A translation memory match Where Studio has already put a TM hit in the segment – a pre-translated or auto-propagated row – that translation goes to the AI as work you have already approved, so it is followed rather than quietly rewritten. Two limits worth knowing, because they are easy to assume away: * It is the match **Studio left on the segment**, not a search of your TMs for the best few. A segment with no TM origin contributes nothing here, so pre-translating before a batch run is what gives this layer anything to say. * **Batch Translate sends exact matches only.** Studio records how close a match is but not the source it was made for, so a fuzzy could only be offered as a translation of a sentence the model cannot read – unable to tell which words differ, and most misleading precisely where a memory has been padded with near-misses to manufacture matches. At 100% the match’s source *is* the segment’s source, so nothing is hidden. Chat, QuickLauncher and AutoPrompt still send whatever match is on the segment, with its percentage. **Toggles:** **Send 100% TM matches to the AI** on the Batch Operations tab, for a job whose memory you do not trust; AI Settings → *Include TM matches* for the rest. ### 6. Termbase terms Matched terms from your active termbases, with approved translations and synonyms, and optionally definitions, domains and usage notes. Non-translatable and forbidden terms are flagged so the AI respects them. Both Supervertaler termbases and MultiTerm `.sdltb` termbases attached to the project contribute. See [TermLens](/trados/termlens/) and [MultiTerm Support](/trados/multiterm-support/). **Toggles:** AI Settings → *Include termbase terms* / *Include term metadata* / the per-termbase contribution list. ### 7. SuperMemory [**SuperMemory**](/trados/ai-assistant/super-memory/) is where you record the things about a client that cannot be looked up. If a bank is active, its files go out with every AI call: * `brief.md` – who the client is and anything standing * `terminology.md` – term decisions, one table * `style.md` – prose rules and approved boilerplate The `_shared` bank is sent alongside as house defaults, and the active bank is marked as overriding it where the two disagree. Where a termbase gives the AI flat pairs of terms, SuperMemory gives it the **reasoning** behind them: the decisions, the caveats, the client-specific overrides. Only the active bank is used (plus `_shared`), so switch to the right one before translating. **Toggles:** AI Settings → *Include memory bank context* / *Use memory bank in AutoPrompt*. ### 8. List numbering Word numbers claims, letters steps and bullets lists as paragraph properties, not as text – so the segment grid never contains the `a)` or the `9.`, and neither did anything the AI received. On a real patent that produced a model reading six unlettered steps, translating “steps a. to f.” faithfully, and then flagging it as a possible defect in the source: a note that would have reached the client. Batch Translate, Translate Segment, Clipboard Mode and SuperBench now prefix the first segment of each numbered paragraph with the marker Word renders, inside a sentinel – `[#e)]`, `[#9.]`, `[#•]` – and a rule in Supervertaler’s own preamble tells the model it is structure, to be used for cross-references and parallelism and never reproduced. Anything the model echoes back is stripped before the target is written. The markers are read from the original Word file Studio keeps inside the sdlxliff and computed for the whole document at once, so a list restarting at claim 11 reads `11.` and lettered steps that continue across claims keep counting, exactly as Word shows them. Always on from v18.20.189; see [Batch Operations](/trados/batch-operations/#list-numbering-as-structure-context). ### 9. Figure descriptions The AI reads your text and cannot see your pictures. [**FigureLens**](/trados/batch-operations/#figurelens-from-v1820189) closes that gap: it takes the images out of the project’s Word documents into a folder, shows each one to the AI together with what the document says about it, and saves a description – what it shows, which figure it is, which parts and reference numbers appear on it – as `figures.md` in the active memory bank. From then on it rides along with layer 7 and is read with every request, so the model knows that the “valve (12)” in the sentence is the thing at the top right of Figure 3. Vector drawings (EMF, WMF – what a drawing placed from CAD usually is) are rendered to PNG on the way out, because no AI can read a metafile. Two clicks per project, then it is automatic. One AI request per image; the button says how many and to which provider before you click, and **Describe from the text only** is a free alternative that uses what the document itself says about each figure. ### 10. Attached files Files you attach to a chat turn – images by paste, drag-drop or browse, and documents (DOCX, PDF, PPTX, XLSX, CSV, TMX, SDLXLIFF, TBX, TXT, Markdown, HTML and more). Images go through each provider’s vision API; documents are text-extracted and appended. Attachments apply only to the turn you attached them on. See [File Attachments](/trados/ai-assistant/file-attachments/). ## Stacking the layers All ten combine freely, and the default composition – everything above except the two that need a click – is a strong baseline and the one to start from. More context is not automatically better, though. The context window is finite, and a large project with a rich termbase and a mature memory bank can push a prompt into the 50 000–100 000-token range. At some point: * adding **TM matches** on top of a memory bank that already knows the client’s preferred wordings may add noise rather than signal; * including **full document content** for a very long document may leave too little room for the memory bank to load; * layering **three overlapping sources** (TM + termbase + memory bank) on the same concept may produce contradictions the AI has to reconcile on the fly. The four layers that describe the *document* rather than the *client* – 3, 4, 8 and 9 – behave differently: they are cheap, they never contradict each other, and there is no case yet found where turning one off improved a translation. Caution We have not published composition presets (e.g. “Mature client – memory bank only”, “Unfamiliar domain – TM + termbase”). Until we do, leave everything enabled and experiment per project. If you find a configuration that works well, say so in [GitHub Discussions](https://github.com/orgs/Supervertaler/discussions). ## Seeing and controlling the layers To see exactly what is being sent, click **👁 Preview prompt** next to the Translate button on the Batch Operations tab. It opens a read-only dialog with the assembled prompt – every layer, in the order the model receives it – and makes no AI call. To change what is sent, open the settings dialog’s **AI Settings** tab, where you can toggle document content, TM matches, term metadata and memory bank context, and choose which termbases contribute. ## See Also * [Supervertaler Assistant](/trados/ai-assistant/) – overview * [Batch Operations](/trados/batch-operations/) – Preview prompt, FigureLens, list numbering * [AI Settings](/trados/settings/ai-settings/) – the toggles * [SuperMemory](/trados/ai-assistant/super-memory/) – the client decisions you record by hand * [SuperMemory → AI Integration](/trados/ai-assistant/super-memory/ai-integration/) – the loading algorithm and token budget * [File Attachments](/trados/ai-assistant/file-attachments/) – add images and documents to a chat turn * [TermLens](/trados/termlens/) – how termbase terms are matched and loaded # User Data Folder Supervertaler for Trados shares a user data folder with [Supervertaler Workbench](https://supervertaler.com/workbench). This allows both programs to access the same termbases, translation memories, and prompt library without duplicating files. ## Folder Location By default, the shared data folder is located at: ```plaintext C:\Users\\Supervertaler\ ``` You can choose a different location during first-run setup. Both programs read the configured path from the same pointer file at `%APPDATA%\Supervertaler\config.json`. ## Folder Structure ```plaintext Supervertaler/ │ ├── prompt_library/ Shared │ ├── domain_expertise/ │ ├── project_prompts/ │ └── style_guides/ │ ├── resources/ Shared │ ├── supervertaler.db │ ├── termbases/ │ ├── tms/ │ ├── non_translatables/ │ └── segmentation_rules/ │ ├── workbench/ Supervertaler Workbench only │ ├── settings/ │ │ ├── settings.json │ │ ├── themes.json │ │ ├── shortcuts.json │ │ └── ... │ ├── dictionaries/ │ ├── projects/ │ ├── ai_assistant/ │ ├── voice_scripts/ │ └── web_cache/ │ └── trados/ Supervertaler for Trados only ├── settings/ │ ├── settings.json │ ├── license.json │ └── chat_history.json ├── projects/ └── batch_backups/ ``` ### Shared resources The **prompt library** and **resources** folders are shared between both programs. Prompts you create or edit in one program are immediately available in the other. The SQLite database (`supervertaler.db`) holds your termbases and translation memories – Workbench has full read-write access, while the Trados plugin reads from it. ### Program-specific folders Each program stores its own settings, projects, and runtime data in a dedicated subfolder (`workbench/` or `trados/`). This keeps configuration separate so the two programs never interfere with each other. The `trados/batch_backups/` folder contains automatic TMX backup files created during Batch Translate runs. One file is written per run, named by timestamp and project name. These files are not deleted automatically – you can remove old ones manually once your project is safely delivered, or keep them as a translation archive for use in other CAT tools. See [Batch Translate – Backup TMX](/trados/batch-translate/#backup-tmx) for details. ## Automatic Migration If you are updating from an older version, both programs will automatically reorganise the folder on their next startup. No manual action is required – your settings, licence, and data are preserved. # AutoPrompt AutoPrompt uses AI to analyse your entire project and generate a comprehensive, domain-specific translation prompt tailored to your document. The generated prompt includes terminology rules, style guidelines, anti-truncation controls, and domain-specific instructions – ready to use with Batch Translate. ![]() #### How It Works **1. Start the analysis** On the **Batch Operations** tab, click the **AutoPrompt…** link next to the prompt dropdown. **2. What gets analysed** Supervertaler gathers the following data from your project and sends it to your configured AI provider: | Data | Purpose | | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **All source segments** | Domain detection, document content analysis, project context | | **Termbase terms** | Filtered to only document-relevant terms (TermScan), then included as a locked termbase in the generated prompt | | **Translated segments** | Human-confirmed segments only (Translated, Approved, or Signed-off status) – used as TM reference pairs and style anchors. Unconfirmed AI-generated translations are excluded. | | **Language pair** | Embedded in the generated prompt | **2b. TermScan – automatic termbase extraction** Before building the prompt, AutoPrompt runs **TermScan**: it concatenates all source segments in the document and checks each termbase entry against this text. Only terms whose source term, source abbreviation, or source synonyms actually appear in the document are included in the generated prompt. This dramatically reduces the termbase size – for example, a general patent termbase with 2,680 entries might yield only 123 relevant terms for a specific document. The status message in the AI Assistant confirms the filter: *“Termbase terms (filtered 123 relevant from 2,680 total)”*. The filtering is case-insensitive and checks all variants of each term (source term, abbreviation forms, and synonyms). Terms that do not appear anywhere in the source text are excluded entirely. Caution **TermScan filters by content, not by domain.** A patent termbase contains many common technical words – “system”, “board”, “fan”, “screen”, “installation” – that will match nearly any engineering document. TermScan will include those entries even though they belong to a completely different translation context, and the AI will be forced to follow them. **Before running AutoPrompt, disable every termbase that does not belong to the current project’s domain.** Use [AI Settings](/trados/settings/ai-settings/) → *Termbases included in AI prompts* to control which termbases contribute to the generated prompt without affecting your TermLens display. Caution **Termbase quality matters.** Only enable termbases in [AI Settings](/trados/settings/ai-settings/) if you are confident they contain accurate, high-quality terminology for your project. A poorly maintained termbase with incorrect or outdated translations will constrain the AI and produce worse results. Modern LLMs – especially Opus-class and GPT-4-class models – are often better at choosing the right translation on their own than when forced to follow a low-quality termbase. When in doubt, disable termbases and let the AI translate freely, then add terms incrementally as you review. **3. Domain detection** Before sending to the AI, AutoPrompt runs a local keyword-based analysis to detect the document’s domain. Supported domains: * **Patent** – claims, embodiments, prior art, figure references * **Legal** – contracts, clauses, statutory references * **Medical** – clinical terms, dosages, ICD/ATC codes * **Technical** – specifications, software terms, standards * **Financial** – figures, IFRS/GAAP, regulatory language * **Marketing** – brand, audience, campaign language * **General** – fallback for mixed or unclassified content The detected domain determines which template the AI uses to generate the prompt – including domain-specific roles, rules, and section structure. **4. Review and refine in the AI Assistant** The generated prompt appears as a message in the **AI Assistant** chat. You can: * **Read through the prompt** to verify it matches your project * **Ask follow-up questions** to refine specific sections (e.g., “Make the termbase section more strict” or “Add a rule about chemical formula formatting”) * **Iterate** as many times as needed – each refinement builds on the conversation history **5. Save the prompt** When you are satisfied with the generated prompt: 1. **Right-click** the assistant message containing the prompt 2. Select **Save as Prompt…** 3. Enter a name for your prompt (e.g., “DLCH Patent NL-EN”) 4. Click **Save** The prompt is saved to the **Translate** category in the Prompt Manager and immediately appears in the prompt dropdown on the Batch Operations tab. #### Translator’s Comment methodology (always-on) Since v4.19.111, every AutoPrompt-generated prompt embeds the **Translator’s Comment** (TC) methodology by default, regardless of source language or domain. The methodology asks the translator AI to silently correct obvious mechanical defects in the source (typos, broken words, hanging mid-sentence breaks, doubled spaces, stray punctuation, reference-numeral mismatches that are unambiguous in context, missing diacritics, etc.) and append a single concise comment at the end of the segment in this exact format: ```plaintext ⟦TC: short factual description of the fix(es)⟧ ``` * The brackets are the mathematical white square brackets **U+27E6** (⟦) and **U+27E7** (⟧). These characters do not occur in source documents, so they are safe as out-of-band markers that can be extracted reliably in post-processing. * One marker per segment maximum; multiple fixes are joined with semicolons inside one marker. * Segments with no defects emit no marker. * When the translator AI inserts a word or short phrase to fill a clear gap, that supplied text is wrapped in standard ASCII square brackets `[like this]` inside the running translation, and the trailing marker references it (e.g. `⟦TC: [bracketed text] supplied to close hanging sentence⟧`). * Numerical values, dates, dosages, claim language, statutory references, headings, identifiers, and proper names are never silently “corrected” – defects in those zones are preserved verbatim, with an optional `⟦TC: source ambiguous – ...⟧` marker if doubt exists. The defect categories that count as “obvious” are adapted to the actual source language by the LLM (Dutch -d/-t verb typos, German missing umlauts, French accent slips, Spanish/Italian conjugation typos, etc.). Caution **Want a generated prompt without the TC methodology?** Edit the generated prompt in the Prompt Manager after creation and remove the TRANSLATOR COMMENT FORMAT section plus any TRANSLATION MANDATE language about silent correction. A per-project opt-out via a UI toggle may be added in a future version – open an issue if you’d like to see it. #### What the Generated Prompt Contains A generated prompt follows the structure of professional translation prompts used by experienced translators. Depending on the domain, it typically includes: * **Role** – domain-specific translator role with expertise areas * **Translation mandate** – strict rules against simplification, paraphrasing, or “improving” the source * **Anti-truncation controls** – explicit prohibition of omitting repetitive phrases or collapsing clauses * **Input handling rules** – instructions for segment-by-segment translation in Supervertaler * **Domain-specific style rules** – mandatory term mappings, register requirements, formatting rules * **Terminology hierarchy** – priority order: TM matches > project termbase > domain conventions * **Preflight self-check** – internal verification step before producing output * **Post-translation integrity assertion** – completeness and faithfulness check * **Project context** – AI-generated summary of what the document is about * **Project-specific termbase** – all termbase terms, marked as locked and mandatory * **TM reference translations** – validated translation pairs as style anchors * **Output format** – translation only, no commentary, preserve formatting #### Tips **Start with a confirmed translated sample** The generator includes **confirmed** segments (Translated, Approved, or Signed-off status) as reference pairs – up to 50, sampled evenly across the document. This gives the AI concrete examples of your preferred style and terminology, resulting in a more accurate prompt. Unconfirmed segments (e.g. from a previous AI batch translation that you haven’t reviewed yet) are excluded to avoid feeding unverified output back as “correct” references. **Tip:** Before generating a prompt, confirm a handful of segments you are happy with. Even 10–20 confirmed segments give the AI meaningful style anchors to work from. **Only enable termbases that belong to this project** Before clicking AutoPrompt, go to **AI Settings → Termbases included in AI prompts** and enable only termbases that are directly relevant to the current project. Disable everything else – including large general-purpose termbases, termbases from other clients or domains, and any termbase you are not actively maintaining for this project. This setting is independent of your TermLens display: disabling a termbase for AI context does not hide its chips in the editor. You can keep a termbase visible for reference while excluding it from the generated prompt. **Review the termbase section** The generated prompt includes only the document-relevant terms extracted by TermScan from your enabled termbases. Check that the termbase accurately reflects your terminology preferences. You can ask the AI to reorganise terms by category or add missing mappings. Caution If your termbase contains incorrect or low-quality entries, these will be injected into the prompt and the AI will be forced to follow them. Only enable termbases that you trust. When starting a new project with no established terminology, consider disabling termbases entirely and letting the AI translate freely – then add terms as you review. **Use with Batch Translate** After saving the generated prompt, select it from the prompt dropdown on the Batch Operations tab. It works with all scopes and providers, just like any other prompt. **AutoPrompt always uses your configured AI provider** [Clipboard Mode](/trados/clipboard-mode/) does **not** apply to AutoPrompt – ticking the Clipboard Mode checkbox affects only the actual Translate / Proofread passes, not prompt generation. AutoPrompt always sends the meta-prompt request to whichever provider is selected in [AI Settings](/trados/settings/ai-settings/). This enables a useful pattern: keep Clipboard Mode ticked, click AutoPrompt to generate the prompt via your paid API, then run the bulk Translate via clipboard against a free web-tier model. See [Combining with AutoPrompt – the hybrid pattern](/trados/clipboard-mode/#combining-with-autoprompt--the-hybrid-pattern) for the full workflow. **Regenerate when the project changes** If your project evolves significantly (new terminology, different document sections, additional termbases), run AutoPrompt again to generate an updated prompt. *** #### See Also * [Batch Translate](/trados/batch-translate/) * [Prompts](/trados/settings/prompts/) * [Supervertaler](/trados/ai-assistant/) * [AI Settings](/trados/settings/ai-settings/) # Getting Started This page walks you through the first-time setup so you can start using TermLens terminology and AI translation inside Trados Studio. ## First-Time Setup ### 1. Open Settings Click the **gear icon** in the TermLens panel header to open the settings dialogue. ### 2. Configure Termbases (TermLens tab) On the **TermLens** tab: 1. Click **Browse** to select an existing Supervertaler termbase (`.db` file) 2. Or click **New** to create a new empty termbase You can add multiple termbases. Designate one as the **Project termbase** to give its terms higher priority (shown in pink). ### 3. Configure AI (AI Settings tab) On the **AI Settings** tab: 1. Select a **provider** (OpenAI, Anthropic, Google, OpenRouter, Ollama, or others) 2. Enter your **API key** for the selected provider 3. Choose a **model** ### 4. Click OK Settings are saved and applied immediately. ## Try It Out ### TermLens 1. Open a project in the Trados **Editor** view 2. Navigate to any segment – TermLens automatically displays term matches for the source text 3. Click a term translation to insert it into the target, or press **Alt+1** through **Alt+9** ### Clipboard Mode (no API key needed) 1. Open the **Supervertaler Assistant** panel and switch to the **Batch Operations** tab 2. Tick the **Clipboard Mode** checkbox 3. Click **Copy to Clipboard** – a ready-to-use prompt with your segments, terminology, and instructions is copied 4. Paste it into any web-based AI (ChatGPT, Claude, Gemini, etc.) and send it 5. Copy the AI’s response and click **Paste from Clipboard** – the translations are written back into Trados See [Clipboard Mode](/trados/clipboard-mode/) for the full walkthrough. ### AI Translate (API key required) 1. Place the cursor in a segment 2. Press **Ctrl+T** to translate the active segment with AI 3. The AI translation appears in the target cell ### Supervertaler 1. Open the **Supervertaler Assistant** panel (View > Supervertaler Assistant) 2. Switch to the **Chat** tab 3. Type a question about the current segment and press **Enter** 4. The assistant responds with context from your terminology and TM matches ## Quick Links | Feature | Page | | ----------------------------- | ------------------------------------------------- | | TermLens terminology display | [TermLens](/trados/termlens/) | | AI via clipboard (no API key) | [Clipboard Mode](/trados/clipboard-mode/) | | AI chat interface | [Supervertaler](/trados/ai-assistant/) | | Bulk AI translation | [Batch Translate](/trados/batch-translate/) | | All shortcuts | [Keyboard Shortcuts](/trados/keyboard-shortcuts/) | *** ## See Also * [Installation](/trados/installation/) * [Clipboard Mode](/trados/clipboard-mode/) * [TermLens](/trados/termlens/) * [Supervertaler](/trados/ai-assistant/) # Import/Export The **Import/Export** tab in the Supervertaler Assistant panel exports the active Trados document’s segments to a proofreader-friendly file (Word DOCX, Bilingual Text, or HTML), then re-imports the proofreader’s edits back into Trados with a confirmation diff.  This is the workflow you’d use for: * **External review** – send a bilingual DOCX to a colleague who doesn’t have Trados, get it back with edits, apply. * **Quick AI proofreading via web LLM** – copy the bilingual text into ChatGPT/Claude/Gemini, paste the corrected version back, re-import. * **Multi-file project review** – export every file in a merged project into one combined DOCX with section breaks between each source file. ## Formats The export offers three formats, matching the Supervertaler Workbench: | Format | Re-importable | When to use | | --------------------------------------- | ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Word document (.docx)** | ✅ | The default. A 5-column bilingual table (`#`, source, target, status, notes) the proofreader edits in Word. Identical to the Workbench’s [Bilingual Table](/workbench/import-export/bilingual-tables/), so files move between both products. | | **Bilingual Text (AI-friendly) (.txt)** | ✅ | A compact plain-text format – one block per segment – ideal for pasting into ChatGPT / Claude / Gemini or editing in any text editor. Identical to the Workbench’s [Bilingual Text](/workbench/import-export/bilingual-text/). | | **HTML report (.html)** | ❌ | Client-facing read-only report. Cannot be re-imported. | There’s no separate “layout” picker: each format has one shape – DOCX and HTML use the 5-column table, and Bilingual Text uses the bracketed `[SEGMENT NNNN]` blocks below. ## The Bilingual Text format Each segment is one block, blank-line separated, with 2-letter language codes labelling the source and target lines: ```plaintext [SEGMENT 0001] EN: MASHUP APPLICATION PROCESSING SYSTEM NL: MASHUP-APPLICATIEVERWERKINGSSYSTEEM [SEGMENT 0002] EN: FIELD OF THE INVENTION NL: GEBIED VAN DE UITVINDING ``` * The `EN:` line is the **source** – leave it alone. It stays on **one line**; a `[newline]` token in it marks where the original source broke across two lines (read-only reference, never written back). * The `NL:` line is the **target** – edit it freely, but **keep it on one line**. Where the target needs a hard line break (e.g. to split a subtitle across two lines), write the literal token `[newline]`; on re-import it’s turned back into a real break. Older files that wrapped a field over several physical lines still re-import unchanged. * The `[SEGMENT NNNN]` markers are the alignment anchors – don’t rename them. Because each field is one labelled line (not a table column), it survives pipe characters and long inputs without the source/target roles getting confused, and keeping targets to one line stops an LLM from accidentally reflowing them. This matches the Workbench’s Bilingual Text export byte-for-byte, so a file produced by either tool round-trips through the other. ## Inline formatting markers Source and target cells use semantic placeholders for inline formatting so the proofreader can move them around without breaking Trados: * `...` – bold pair * `...` – italic pair * `...` – underline pair * `...` – bold + italic pair * `...`, ``, … – numbered placeholders for everything else (field codes, page numbers, custom format pairs) In the DOCX, the markers render in red and the text between a semantic pair is shown in matching bold / italic / underline so the proofreader can see what the formatting will look like. **Round-trip rules:** * Semantic markers (`` / `` / `` / ``) can be freely **added, removed, or reordered** in the target – they only affect cosmetic rendering and don’t drive Trados QA. * Numbered structural markers (``, ``, …) **must round-trip exactly**. Adding a `` the source doesn’t have, or dropping one the source requires, would break the Trados file. The importer counts numbered markers on both sides and skips any segment whose count has changed (with a per-segment log entry). The **“Refuse to apply edits that drop source-required tags”** checkbox enables this strict check. Leave it on unless you know what you’re doing. ## Multi-file projects When the active Trados editor view contains more than one file merged (common when the Trados project was prepared with file merging), the tab grows extra controls: ### Files to export A checkbox list of every file in the active document, each with its segment count. Quick-select buttons: * **Active only** – checks only the file your cursor is currently in * **All** – checks every file * **None** – unchecks every file (Segments: 0) The **Segments: N** label tracks the current selection live. ### Output mode * **Combine into one file** (default) – produces a single bilingual file containing all selected files joined together, with a file-boundary marker between each source file so the proofreader can see where one file ends and the next begins. In a **DOCX** the table grows a 6th **File** column with a highlighted ”📄 File: ``” section-break row; in a **Bilingual Text** file a `📄 File: ` marker line prefaces each new file’s first segment. * **Separate file per file** – asks for a folder and writes one bilingual file per selected source file. Single-file documents see no change – the file list, output radio, and per-file UI are all hidden. (On re-import, the DOCX table’s 5- vs 6-column form is auto-detected.) ## Locked segments Trados segments can be **locked** (read-only in the editor) independently of their confirmation level – so a segment can be both `ApprovedTranslation` and locked, or `Draft` and locked. On large projects with a lot of locked-approved content, sending those segments to a proofreader is usually noise: any edits they make there can’t be written back to Trados anyway. A dedicated checkbox controls how the export handles them: > **Include locked segments (🔒 marked in Status column)** – default ON. * **ON (default)** – locked segments are exported alongside everything else, and every locked row gets a **🔒** prefix in the Status column (e.g. `🔒 ApprovedTranslation`). The proofreader can see at a glance which rows aren’t editable round-trippable, and the re-import will refuse to overwrite them. * **OFF** – locked segments are skipped entirely. The exported file only contains rows that are actually still editable. Useful on multi-thousand-segment projects where the bulk of the work is already locked. The checkbox lives right under the **“Refuse to apply edits that drop source-required tags”** option on the tab. **On re-import**, locked segments are honoured regardless of the export-side setting: edits made to a locked row are reported as a *locked-segment* item in the re-import summary’s “other issues” count, and **not** written back to Trados. To genuinely change a locked segment, unlock it in Trados first, then re-import. The locked flag also lives in the sidecar manifest (`is_locked: true` / `false` per segment) so the source of truth for which segments were locked at export time is preserved. ## Filtering by confirmation status Just below the locked-segments option is a **Statuses to include in export** group of six checkboxes – one per Trados confirmation level: * **Unspecified** – not yet translated (the initial state of a fresh segment) * **Draft** – in progress * **Translated** – confirmed by the translator * **Approved (translation)** – first-pass approval * **Approved (sign-off)** – final approval * **Rejected** – marked for rework All six are checked by default – no filter, every segment is included. Untick any subset to narrow the export to just those statuses. Common use-cases: * **Tick only Translated** – send a draft pass to a proofreader. * **Tick only Approved (translation)** – send near-final material out for a sign-off review. * **Untick Approved (sign-off)** – exclude locked-down rows the client has already signed off on, so the proofreader only sees what’s still in play. * **Tick only Draft + Unspecified** – generate a worklist of what’s still unfinished. This filter composes orthogonally with the **Include locked segments** option and the multi-file **Files to export** list – every segment must pass all three filters to make it into the bilingual file. ## Re-import workflow Click **📥 Re-import…**, pick the round-tripped file. Supervertaler: 1. Loads the file’s sidecar manifest (the `.svexport.json` written alongside the export). 2. For each row in the file, looks up the matching segment in Trados via the manifest’s `(ParagraphUnitId, SegmentId)` mapping. 3. Compares the file’s target text against the current Trados target – same serialisation pipeline on both sides, so only real edits register as changes. 4. Counts up: **changes to apply**, **unchanged**, **tag-mismatch** (will be skipped under strict mode), and **other issues** (segment missing, **locked**, source text was tampered with). 5. Shows you a summary dialog with **OK** / **Cancel**. Click **OK** and Supervertaler writes the accepted changes back via the same code path the batch AI translator uses – confirmation level is preserved, and **locked segments are skipped automatically** (the writeback queries `IsLocked` on every segment, so a lock toggled in Trados between export and re-import is also respected). ## Recent exports At the bottom of the tab, a list tracks every export from this session with: * **Open file** – opens the bilingual file in its default app * **Open folder** – opens the containing folder * **Re-import this** – same as the main Re-import button, pre-pointed at this file ## Sidecar manifest Every export writes a small `.svexport.json` file alongside the bilingual file. It contains: * Project name, source filename, language pair, export timestamp, tool version * Per-segment `(number → ParagraphUnitId / SegmentId)` mapping * A SHA-256 prefix of the source text for tamper detection * For multi-file exports: per-segment source file id + name * Per-segment `is_locked: true | false` flag (snapshot at export time) The manifest is what lets re-import find the exact Trados segments even if the proofreader accidentally reorders rows. If the manifest goes missing, re-import falls back to current-document mapping (which loses source-tamper protection but still works). ## See Also * [Batch Operations](/trados/batch-operations/) – for AI-driven proofreading directly in Trados * [AI Proofreader](/trados/ai-proofreader/) – in-Trados proofreading mode # Installation ### Installation #### Download **Install Supervertaler for Trados from the [RWS App Store](https://appstore.rws.com/plugin/432).** This is the recommended route for everyone: every published build is RWS-signed, so Trados loads it without the “Unsigned Trados Studio Plug-in Found” warning that appears – *every time Studio starts* – for a plugin installed from anywhere else. You can either install from inside Trados Studio (**Add-Ins > RWS App Store**, search for “Supervertaler”, click **Download**) or download the `Supervertaler for Trados.sdlplugin` file from the [App Store website](https://appstore.rws.com/plugin/432) and double-click it. Either path opens the Trados Plugin Installer. #### Install 1. **Close Trados Studio** if it is running 2. **Double-click** the downloaded `Supervertaler for Trados.sdlplugin` file 3. The Trados Plugin Installer opens – select your Trados Studio version and choose an installation location:  The Trados Plugin Installer lets you choose which Trados version to install for and where to place the plugin. 4. Click **Next**, then **Finish** to complete the installation 5. **Start Trados Studio** – the plugin loads automatically **Installation locations** The installer offers three options for where to place the plugin. Each option stores the plugin in a different Windows folder, which determines who can use it and whether it follows you to other computers. The paths below are for **Trados Studio 2024**. For **Studio 2026** every path is identical except that `\18\` becomes `\19\`. **“All your domain computers”** (default) : Installs to: `C:\Users\\AppData\Roaming\Trados\Trados Studio\18\Plugins\Packages\` : The Windows **Roaming** profile folder. In environments that sync the Roaming profile across machines – classic Active Directory roaming profiles, FSLogix profile containers, and similar setups – the plugin follows your Windows account from one PC to another. (OneDrive Known Folder Move does **not** sync `AppData\Roaming` by default, so OneDrive on its own is not a roaming mechanism.) On a single-PC personal install without any profile-sync setup, the plugin simply stays on the machine – functionally similar to “This computer for me only”, though the folder is still `Roaming` rather than `Local`, which can matter if the machine later joins a profile-sync environment. **“This computer for me only”** : Installs to: `C:\Users\\AppData\Local\Trados\Trados Studio\18\Plugins\Packages\` : The Windows **Local** profile folder. The plugin stays on this specific machine and is only available to your Windows user account. If another person logs into the same PC with a different Windows account, they will not have the plugin. **“This computer for all users”** : Installs to: `C:\ProgramData\Trados\Trados Studio\18\Plugins\Packages\` : The shared **ProgramData** folder. The plugin is available to every Windows user account on this machine. Use this on shared workstations where multiple people log in with their own Windows accounts and all need the plugin. Rarely needed for most translators. **“Remove this plugin from all installation folders” checkbox** The Trados Plugin Installer shows a checkbox below the install-scope radio buttons: > ☑ **Remove this plugin from all installation folders** *(recommended if you installed manually or multiple times)* It is ticked by default. **Always leave it ticked.** Before placing the fresh install in the location you’ve selected, the installer sweeps all three locations (Roaming, Local, ProgramData) and removes any existing Supervertaler copies. On a first-time install there’s nothing to remove and the checkbox is a harmless no-op; on an upgrade or after a previous manual install, it prevents the multi-scope-orphan problem where Trados ends up with two copies of the plugin in different folders and loads the wrong one on next start. #### Verify Installation After restarting Trados Studio, open a project in the Editor view. You should see: * **TermLens panel** – docked above the editor area (or in the bottom panel area) * **Supervertaler Assistant panel** – docked on the right side **If the TermLens panel is not visible** Go to **View > TermLens** to show the panel. **If the Supervertaler Assistant panel is not visible** Go to **View > Supervertaler Assistant** to show the panel. #### Free up the keyboard shortcuts Trados Studio’s own default bindings sit on several of the key combinations Supervertaler uses (`Ctrl+Alt+T`, `Ctrl+Alt+N`, `Ctrl+Alt+G`, `Alt+Up`, `Alt+Q`) – and the Trados binding wins, so those Supervertaler shortcuts do nothing until you clear the defaults. This takes two minutes in **File → Options → Keyboard Shortcuts** and only needs doing once per Trados installation. See [First-time setup: free up Trados shortcuts](/trados/keyboard-shortcuts/#first-time-setup-free-up-trados-shortcuts) for the full table of what to delete. #### Running on a Mac (Parallels) If you are running Trados Studio inside **Parallels Desktop** on a Mac, there is one important rule for the first-run setup: **Keep your data folder on the Windows side** – use the default path (e.g., `C:\Users\\Supervertaler`). Do **not** point it to a Mac-side path like `\\Mac\Home\Supervertaler`. Supervertaler stores termbases as SQLite databases, and SQLite requires a local filesystem to work reliably. The `\\Mac\Home\...` paths in Parallels are mounted via a virtual network share, which can cause database locking errors or data loss. Caution **Mac users:** When the first-run setup dialogue appears, accept the default `C:\Users\\Supervertaler` path. If you previously used Supervertaler Workbench on the Mac side, copy your termbases into the Windows-side folder rather than pointing to the Mac path directly. The plugin automatically detects Parallels and shows a warning if you select a Mac-side path during setup. **Sharing termbases between Workbench and the Trados plugin on a Mac** On Windows, both Supervertaler Workbench and the Trados plugin can point to the same shared data folder and work from the same `.db` termbase file simultaneously. On a Mac with Parallels, this is **not possible** because the two products run on different filesystems: * **Supervertaler Workbench** runs natively on macOS – its data folder is on the Mac filesystem (e.g., `/Users//Supervertaler/`) * **Supervertaler for Trados** runs inside Parallels (Windows) – its data folder must be on the Windows filesystem (e.g., `C:\Users\\Supervertaler\`) The Trados plugin cannot reliably use a Mac-side path (`\\Mac\Home\...`) due to SQLite limitations on virtual network shares. To keep your termbases in sync between the two products on a Mac, copy the `.db` file from one side to the other after making changes. This is a limitation of the Parallels virtualisation layer, not of the termbase format. *** #### Updating When a new version is published to the App Store, Supervertaler shows an **Update Available** dialogue on the next Trados startup, with the version difference and an **Install Update** button. 1. Click **Install Update** – the plugin downloads the RWS-signed update from the App Store and writes it back to the same install scope (Roaming, Local, or ProgramData) you originally chose during installation 2. When prompted, click **Restart Trados Studio** – the plugin restarts Trados for you and loads the new version Your settings, termbases, prompts, memory banks, and licence key are all preserved across updates – no need to uninstall first. **Manual update from the App Store website** If you’ve dismissed the in-plugin dialogue (for example, by clicking **Remind Me Later**) and want to update straight away, you can install manually from the App Store website: 1. **Close Trados Studio completely** – the plugin files are locked while Trados is running 2. Open the [App Store page for Supervertaler](https://appstore.rws.com/plugin/432) and click **Download** to save the latest `Supervertaler for Trados.sdlplugin` 3. Double-click the file – the Trados Plugin Installer handles the rest 4. Start Trados Studio – the new version loads automatically Caution Trados Studio **must be fully closed** before installing or updating manually. If Trados is still running, the installer may silently fail because the plugin files are locked. #### Troubleshooting: old version still showing after update If Trados still loads an older version of the plugin after installing a new one, an old copy may be lingering in a different installation location. Check all three plugin folders and remove any old `Supervertaler for Trados.sdlplugin` (in `Packages`) and `Supervertaler.Trados` folder (in `Unpacked`): Replace `` with your own Windows user name. Use the block for your Studio version – `18` is Studio 2024, `19` is Studio 2026. Each path is one of the three choices the Trados Plugin Installer offers under “Please select the folder where the plugin will be installed”, so if you remember which you picked, start with that one – but check all three, because an earlier install may have used a different one. **Trados Studio 2024** ```plaintext C:\Users\\AppData\Roaming\Trados\Trados Studio\18\Plugins\ <- "All your domain computers" (the default) C:\Users\\AppData\Local\Trados\Trados Studio\18\Plugins\ <- "This computer for me only" C:\ProgramData\Trados\Trados Studio\18\Plugins\ <- "This computer for all users" ``` **Trados Studio 2026** ```plaintext C:\Users\\AppData\Roaming\Trados\Trados Studio\19\Plugins\ <- "All your domain computers" (the default) C:\Users\\AppData\Local\Trados\Trados Studio\19\Plugins\ <- "This computer for me only" C:\ProgramData\Trados\Trados Studio\19\Plugins\ <- "This computer for all users" ``` Inside each one there are two folders that matter, and **both** need clearing: * `Packages` holds the installed `.sdlplugin` file. * `Unpacked` holds the files Studio actually loads, extracted from it. This is the one people miss, and it is the one that blocks a reinstall: Studio will not re-extract over an `Unpacked` folder that is already there. After removing the old files, double-click the new `.sdlplugin` to install it fresh, then start Trados. #### Uninstalling To remove the plugin: 1. Open Trados Studio 2. Go to **Help > Plugin Management** 3. Find “Supervertaler for Trados” in the list 4. Click **Uninstall** 5. Restart Trados Studio *** #### Next Steps * [Getting Started](/trados/getting-started/) – set up your first termbase and API key # Keyboard Shortcuts All keyboard shortcuts available in Supervertaler for Trados, with Mac equivalents for users running Trados in Parallels. ## First-time setup: free up Trados shortcuts Trados Studio ships with its own default bindings on several of the key combinations Supervertaler uses – and the Trados binding wins. If a Supervertaler shortcut does nothing, this is almost always why. Go to **File → Options → Keyboard Shortcuts**, search for the Trados action named below, and delete (or reassign) its binding: | Shortcut | Trados default action (delete its binding) | Supervertaler action that needs it | | ------------ | ------------------------------------------ | ------------------------------------ | | `Ctrl+Alt+T` | Insert TM Symbol (™) | Add term entry (full editor) | | `Ctrl+Alt+N` | New Cloud Project | Quick-add non-translatable term | | `Ctrl+Alt+G` | Open GroupShare Project | Auto-tag active segment (AutoTagger) | | `Alt+Up` | Focus Previous Row | Quick-add term to project termbase | | `Alt+Q` | Tell me what you want to do | Open QuickLauncher | ## Terminology | Shortcut (Windows) | Shortcut (Mac) | Action | | ------------------ | ----------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `Alt+Down` | `Option+Down` | Quick-add term to write termbases | | `Alt+Up` | `Option+Up` | Quick-add term to project termbase | | `Ctrl+Alt+T` | `Control+Option+T` | Add term entry (opens full editor with definition, domain, notes, URL, client, project, and synonyms) | | `Ctrl+Alt+A` | `Control+Option+A` | [Add term with abbreviation](/trados/termlens/adding-terms/) – the AI fills in the term pair and both abbreviations from the segment, for you to confirm (from v18/19.20.157) | | `Ctrl+Alt+N` | `Control+Option+N` | Quick-add non-translatable term | | `Ctrl` (tap) | `Control` (tap) | Toggle the floating **TermLens popup** (open / close) | | `Alt+P` | `Option+P` | Open **TermPicker** (list-based) – or focus the TermPicker pane when it is docked | | `Alt+1` … `Alt+9` | `Option+1` … `Option+9` | Insert term 1–9 by badge number | ## AI Translation | Shortcut (Windows) | Shortcut (Mac) | Action | | ------------------ | -------------- | --------------------------------------------------------------------------------------------------------------------- | | `Alt+Q` | `Option+Q` | Open QuickLauncher prompt menu | | `Alt+T` | `Option+T` | Translate the active segment (uses Batch Translate settings, incl. document + SuperMemory context from v18/19.20.149) | ## Voice Commands | Shortcut (Windows) | Shortcut (Mac) | Action | | ------------------ | ------------------ | --------------------------------------------------------------------------------------------------------------- | | `Ctrl+Alt+D` | `Control+Option+D` | Toggle [voice commands](/trados/voice-commands/) on/off (same as clicking the 🎤 button in the TermLens header) | ## QuickLauncher Shortcuts | Shortcut (Windows) | Shortcut (Mac) | Action | | --------------------------- | --------------------------------------- | --------------------------------------------- | | `Ctrl+Alt+1` … `Ctrl+Alt+9` | `Control+Option+1` … `Control+Option+9` | Run QuickLauncher prompt assigned to slot 1–9 | | `Ctrl+Alt+0` | `Control+Option+0` | Run QuickLauncher prompt assigned to slot 10 | ## SuperMemory | Shortcut (Windows) | Shortcut (Mac) | Action | | ------------------ | ------------------ | -------------------------------------------------------------- | | `Ctrl+Alt+M` | `Control+Option+M` | Quick Add – add a term or correction to the active memory bank | ## SuperSearch | Shortcut (Windows) | Shortcut (Mac) | Action | | ------------------ | -------------- | ---------------------------------------------------------------------------------------- | | `Alt+S` | `Option+S` | Open SuperSearch – searches for the selected source/target text across all project files | | `Alt+W` | `Option+W` | Search the web for the selected term, in your project’s language pair | ## AutoTagger | Shortcut (Windows) | Shortcut (Mac) | Action | | ------------------ | ------------------ | ----------------------------------------------------------------------------------- | | `Ctrl+Alt+G` | `Control+Option+G` | Auto-tag the active segment – places the source segment’s inline tags in the target | ## Navigation and Display | Shortcut (Windows) | Shortcut (Mac) | Action | | ------------------ | -------------- | ----------------------------------------------------------------------------------------------------------------- | | `F1` | `F1` | Context-sensitive help | | `F2` | `F2` | Expand selection to word boundaries | | `F5` | `F5` | Force-reload Supervertaler termbases from disk and refresh TermLens display (does not reload MultiTerm termbases) | ## Shortcuts for Terms 10+ When a segment has more than 9 matched terms, you can still insert terms by number using Alt+digit. TermLens offers two shortcut styles – choose the one you prefer in **Settings > TermLens > Term shortcuts**. ### Sequential (default) Type the term number digit by digit. Each badge shows the plain term number (10, 11, 12, …). | Shortcut (Windows) | Shortcut (Mac) | Inserts | | ------------------ | -------------- | ------- | | `Alt+10` | `Option+10` | Term 10 | | `Alt+23` | `Option+23` | Term 23 | | `Alt+45` | `Option+45` | Term 45 | After the first digit, TermLens waits briefly for a possible second (or third) digit. If no further digit is pressed, the single-digit term is inserted. ### Repeated digit Press the **same digit key** multiple times. Each badge shows the repeated digit (11, 222, 3333, …). | Presses | Windows | Mac | Badge | Terms | | ------- | ------------------------- | ------------------------------- | --------------------- | ----- | | 1x | `Alt+1` … `Alt+9` | `Option+1` … `Option+9` | **1** – **9** | 1–9 | | 2x | `Alt+11` … `Alt+99` | `Option+11` … `Option+99` | **11** – **99** | 10–18 | | 3x | `Alt+111` … `Alt+999` | `Option+111` … `Option+999` | **111** – **999** | 19–27 | | 4x | `Alt+1111` … `Alt+9999` | `Option+1111` … `Option+9999` | **1111** – **9999** | 28–36 | | 5x | `Alt+11111` … `Alt+99999` | `Option+11111` … `Option+99999` | **11111** – **99999** | 37–45 | *** ## See Also * [TermLens](/trados/termlens/) * [Supervertaler](/trados/ai-assistant/) * [SuperSearch](/trados/supersearch/) * [AutoTagger](/trados/autotagger/) * [Batch Translate](/trados/batch-translate/) * [SuperMemory](/trados/ai-assistant/super-memory/) # Licensing Supervertaler for Trados uses a simple subscription model: one product, one price, everything included. ## Free Trial When you first install Supervertaler for Trados, a **14-day free trial** starts automatically. During the trial, all features are unlocked – TermLens, AI Assistant, SuperSearch, memory banks, Studio Tools, and everything else. No sign-up or credit card is required to start the trial. The remaining days are shown in the **Licence** tab in Settings and in the About dialogue. ## Pricing | | Monthly | Annual | | ---------------------------- | --------- | --------- | | **Supervertaler for Trados** | €20/month | €200/year | One plan, all features included: TermLens inline terminology, AI Assistant & Batch Translate, SuperSearch cross-file search & replace, SuperMemory memory banks, Studio Tools, Clipboard Mode, QuickLauncher, Prompt Library, MultiTerm support, Incognito Mode, and all future features. ## Purchasing a Licence 1. Visit [supervertaler.com/trados](https://supervertaler.com/trados/) and click **Subscribe** 2. Complete the checkout – you will receive a **licence key** by email 3. Open Trados Studio → **Settings → Licence** tab 4. Paste your licence key and click **Activate** Your licence allows activation on up to **2 machines** (e.g. a desktop and a laptop). ## Activating Your Licence 1. Open Trados Studio 2. Click the **gear icon** (⚙) on the TermLens or Supervertaler Assistant panel 3. Go to the **Licence** tab 4. Enter your licence key in the text field 5. Click **Activate** A confirmation message appears when activation succeeds. The Licence tab shows your plan name, masked licence key, status, and last verification date. ## Managing Your Subscription From the **Licence** tab in Settings, you can: * **Verify Now** – manually check your licence status with the server * **Deactivate** – remove the licence from this machine (frees up an activation slot) * **Manage subscription →** – opens the Lemon Squeezy billing portal where you can update payment details or cancel ## Offline Use After activation, the plugin caches your licence status locally. You can work offline for up to **30 days** before the plugin needs to verify your licence again. When you reconnect to the internet, verification happens automatically in the background. ## What Happens When the Trial Expires After the 14-day trial ends: * **No licence** – all features show a “licence required” overlay. Your termbases, settings, and prompt library are preserved. * **Active licence** – all features are unlocked. Activating a licence immediately unlocks all features. ## Changing Machines If you replace a computer or need to move your licence: 1. On the old machine: open **Settings → Licence** and click **Deactivate** 2. On the new machine: enter your licence key and click **Activate** If you can no longer access the old machine, the activation slot will be freed automatically when the licence is next validated. ## Privacy & Security The plugin makes **no network calls** except to: 1. **Your chosen AI provider** (OpenAI, Anthropic, Google Gemini, OpenRouter, or local Ollama) – only when you use AI features 2. **Lemon Squeezy licence API** (`api.lemonsqueezy.com`) – for licence activation and periodic validation 3. **Anonymous usage statistics** (strictly opt-in) – if you consent, a single ping on startup sends only: plugin version, OS version, Trados version, and system locale. See [Usage Statistics](/trados/settings/usage-statistics/) for details. The licence validation sends only your licence key and a hashed machine fingerprint (a one-way hash of your computer name and Windows user ID). No personal data, no translation content, no termbase information is ever collected. Your API keys are stored locally in `%LocalAppData%\Supervertaler.Trados\settings.json` and are never transmitted anywhere except to your chosen AI provider. # Supervertaler MCP Server The Supervertaler MCP Server connects **Claude Desktop** directly to your live Trados Studio session. You chat in Claude’s own window, and it answers from your real project data: the document open in the editor, your translation memories, and your termbases. It can also make changes for you, always under your supervision. > **Which AI apps work?** Any app that can run a **local (STDIO) MCP server on your own machine**. Claude Desktop is the easiest, because the plugin ships a one-click extension for it. **ChatGPT’s desktop app works too** *(confirmed August 2026)*, as do **Google Antigravity** *(confirmed September 2026)*, Claude Code, Gemini CLI and **Mistral Vibe CLI** *(confirmed August 2026)* – see [Setting it up](#setting-it-up) for each. Antigravity is the Google-side equivalent of Claude Desktop, and the way to drive Trados from Gemini. What cannot work is anything that runs the server in the cloud rather than on your PC. That rules out the claude.ai and chatgpt.com **websites**, and also Mistral’s **Vibe web app**, whose custom MCP connectors accept only a remote `https://` URL. The Supervertaler bridge is local by design, so your project never leaves your machine, and a cloud-hosted client has no route to it. > > *Earlier versions of this page said ChatGPT desktop could not be used. That was true when written and is no longer: the desktop app has since added support for local STDIO servers.* MCP ([Model Context Protocol](https://modelcontextprotocol.io/)) is the open standard that lets AI applications securely call tools exposed by other programs. The Supervertaler MCP Server is the first MCP server that talks to a **live** Trados Studio editor session – other Trados-related MCP servers work on project files on disk, not the document you are working on. **Prefer to watch?** The [MCP Server screencast](https://www.youtube.com/watch?v=hKQ62_IU0fk) (9 min) shows it in use: Trados Studio 2026 driven from Claude’s chat window. [Supervertaler MCP Server – controlling Trados Studio 2026 from Claude Chat](https://www.youtube.com/embed/hKQ62_IU0fk)  **Claude Code.** Asking for a glossary drawn from the live Trados Studio project – it reads the open document and checks the user's termbase, then answers in chat.  **And from a phone.** The same project, asked from Claude's Android app: the conversation is attached to Claude Desktop on the PC, where the MCP server runs, so the tools reach Trados Studio just as they do on the desktop. The PC has to stay on with Studio open – but you do not have to be at it. ## What you can ask With Trados Studio open and a document in the editor, you can ask your AI assistant things like: * “What’s the status of my Trados project? How many segments are left?” * “How many times does the word *doekrol* appear in my project, and did I translate it consistently?” * “Find all Draft segments containing *flange* and show me the translations.” * “How did I translate this phrase before?” (searches your Supervertaler TMs) * “What does my termbase say for *sluitkracht*?” * “Draft translations for the untranslated segments and set them to Draft so I can review them.” * “We agreed *draagarm* = *support arm* – add it to my termbase.” * “Work with the 2026 one.” (when you have two versions of Trados Studio open – see [Two Studios open at once](#two-studios-open-at-once-from-v1820184)) Unlike the [AI-friendly bilingual export](/trados/import-export/) workflow, there is no export/re-import cycle: the AI reads the live document on demand, and changes it makes appear in Studio while you chat. ## What the AI can do The server exposes these tools to the AI app: | Tool | What it does | | ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `help` | A curated menu of what you can ask – shown when you say *“what can I do?”* *(v18.20.106)* | | `session_report` | How many bytes of tool results this session has sent the AI, per tool, biggest first – so you can see which tools are filling (and re-billing) the conversation *(v18.20.158)* | | `list_trados_instances` | Which Trados Studios are running, the project open in each, and which one the AI is talking to – for when you have more than one open *(v18.20.184)* | | `select_trados_instance` | Tell the AI which of several running Studios to work with, by Studio version or project name *(v18.20.184)* | | `get_active_project` | Project name, language pair, active file, segment counts per confirmation status | | `get_segments` | List segments, with filters (status, contains-text, file) and paging – or fetch exact segments by the grid number(s) you see in Studio (`fromNumber`/`toNumber`) *(grid numbers v18.20.114)* | | `get_files` | The files of a merged multi-file document, with per-file segment counts *(v18.20.95)* | | `get_active_segment` | The segment you are editing right now, with TM matches and termbase hits | | `get_project_statistics` | Analysis bands and per-file confirmation statistics – word counts, progress *(v18.20.95)* | | `search_studio_tm` | Concordance-search the Trados TMs attached to the project (.sdltm and GroupShare) *(v18.20.95)* | | `lookup_term` | Look up a term in your termbases (exact first – against source and target terms alike – then substring matching); hits report which column matched and are never reoriented *(v18.20.153)* | | `find_inconsistencies` | Repeated source segments whose translations differ *(v18.20.95)* | | `compare_document_to_tm` | Every segment where your translation differs from what the TM already holds for the same source – the pre-delivery consistency check *(v18.20.148)* | | `check_numbers` | Translated segments whose numbers differ between source and target *(v18.20.95)* | | `check_tags` | Translated segments with missing or extra inline tags – compares underlying tag ids as well as counts, so two tags sharing one id are caught *(ids from v18.20.157)* | | `check_terminology` | Translated segments that don’t use the termbase’s expected translation – longest-match-wins, ranked by signal rather than raw count, restrictable to a curated termbase *(overhauled v18.20.157)* | | `check_nbsp` | Translated segments that lost a non-breaking space the source had – invisible on screen, so nothing else catches it *(v18.20.148)* | | `get_coverage` | Which segments have been neither written nor explicitly reviewed this session, per TM match band – so “the fuzzy band was read” becomes checkable instead of remembered *(v18.20.157)* | | `mark_reviewed` | Record that segments were read source-against-target and deliberately left unchanged – session-scoped, never written to the file *(v18.20.157)* | | `get_tracked_changes` | The document’s tracked changes as (before, after) pairs per segment – how you corrected the drafts – optionally saved into the active SuperMemory bank’s reference folder for future projects *(v18.20.158)* | | `list_resources` | The TMs and termbases attached to your project and Supervertaler setup – per termbase with its Read/Write ticks and whether it is the Project termbase *(roles from v18.20.159)* | | `list_projects` | Every project registered in Trados Studio – across Studio 2026/2024/2022 – with status and paths *(v18.20.111)* | | `get_project` | Details of any registered project by name, without opening it *(v18.20.111)* | | `list_tms` | The file TMs on this machine (Studio folders + project references) *(v18.20.111)* | | `list_project_templates` | Your Trados project templates *(v18.20.111)* | | `update_segments` | Write translations and/or set confirmation statuses (see safety rails below) | | `add_term` | Add a term pair to your Write termbases – direction-aware per termbase, with optional definition/domain/notes, termbase targeting by name or by role (project vs background – see below), and a per-termbase echo of exactly what was stored; duplicates echo the existing entry they matched *(scope + duplicate echo v18.20.159)* | | `update_term` | Fix an existing entry in your Write termbases – exact-match; can change the term pair and, from v18.20.159, also the entry’s notes, definition and domain – only the fields you name change, everything else is preserved | | `delete_term` | Remove an entry from your Write termbases – destructive, so the AI confirms first *(v18.20.113)* | | `import_project_termbase` | Copy the Trados termbase attached to the open project (`.sdltb` / `.ttb`) into a Supervertaler termbase in one step – the same job as the *Import .sdltb/.ttb…* button. Ask for a dry run first and it reports the entry count, language pair and field mapping before writing anything; running it twice adds nothing the second time. An existing destination must be Write-enabled, a new name is created for you, and your Trados termbase is only ever read *(v18.20.175)* | | `insert_into_active_segment` | Insert text into the active segment’s target (like Apply-to-target) | | `save_document` | Save the open document (Ctrl+S) – only when you ask or approve *(v18.20.115)* | | `go_to_segment` | Move the Studio editor to a specific segment (by grid number or id) | | `find_and_replace` | Find & replace across the target text – tag-safe, with a preview before applying | | `get_comments` | Read the Trados comments in the document | | `add_comment` | Add a Trados comment to a segment (flag a source issue, leave a review note) | | `update_comment` | Edit an existing Trados comment – its text, its severity, or both *(severity from v18.20.159)* | | `delete_comment` | Remove a Trados comment (or all of a segment’s) – destructive, so the AI confirms first *(v18.20.116)* | | `run_verification` | Run Studio’s Verify Files (QA Checker) and return the findings per segment – flagged as stale if the AI has unsaved edits *(stale flag v18.20.148)* | | `analyze_files` | Run **Analyse Files** – computes the perfect/exact/fuzzy/new/repetition leverage breakdown *(v18.20.106)* | | `pretranslate` | Run **Pre-translate Files** – fill untranslated segments with their TM matches | | `update_tm` | Run **Update Main Translation Memories** – write confirmed segments to the project TM | | `export_target` | Run **Generate Target Translations** – write out the translated target files | | `get_task_status` | Check a background batch task’s progress (analyse, pre-translate, …) *(v18.20.104)* | | `list_prompts` | Browse your Supervertaler prompt library, optionally filtered by folder or search term *(v18.20.101)* | | `get_prompt` | Read the full text of one of your prompts *(v18.20.101)* | | `save_prompt` | Create a new prompt, or update one of your own – built-in defaults are protected *(v18.20.101)* | | `get_prompt_context` | Everything the AI needs to write a translation prompt tailored to your open project – source text, domain, terms, TM examples *(v18.20.109)* | | `get_supermemory_context` | The active [SuperMemory](/trados/ai-assistant/super-memory/) bank for this project – its brief, terminology table and style rules, plus the `_shared` bank of house defaults that the client bank overrides *(three-file banks from v18.20.169)* | | `search_supermemory` | Search your active memory bank **and `_shared`** by keyword – *“what did I decide about this term, and why?”*. Each hit says which bank it came from *(v18.20.146; `_shared` included from v18.20.172)* | | `list_supermemory_banks` | Your memory banks and which one is active. `_shared` is labelled as the always-loaded layer rather than listed as an ordinary bank *(v18.20.146; roles from v18.20.172)* | > The four batch tasks (`analyze_files`, `pretranslate`, `update_tm`, `export_target`) run in the **background** and return immediately – the AI polls `get_task_status` and tells you when they finish, so a long analysis never stalls the chat. > > This list grows over time. For the current set on your installed version, just ask the AI *“what can I do?”* (the `help` tool). ### Safety rails on write actions * Translations written by the AI are set to **Draft** status unless it explicitly sets another status – so you can filter for them in Studio and review everything. * **Locked segments are never touched.** * **Find & replace keeps each segment’s confirmation status** *(from v18.20.148)*. Editing a segment’s content normally demotes it to Draft, which meant a single consistency sweep over a finished file could quietly leave thousands of segments unconfirmed. The AI can still ask for a specific status when you want one. * Updates are limited to 40 segments per call; larger jobs are processed in reported batches. *(Lowered from 200 in v18.20.148: bigger batches could outlast the connection timeout, and because the write had already gone through, the AI couldn’t tell success from failure.)* * Changes land in the open document but are **not saved automatically** – saving stays your decision. From v18.20.115 the AI can run the save for you (`save_document`, same as Ctrl+S), but only when you ask or approve – *“save and run the analysis”* is one instruction, silent saving is not allowed. * The AI is instructed to only make changes you asked for, and to report exactly what it changed. ### Two Studios open at once *(from v18.20.184)* Trados Studio 2024 and Trados Studio 2026 can run side by side, each with its own project and its own connection. Two AI apps can then work on **two different projects at the same time** – ChatGPT drafting one job while Claude Desktop drafts the other, in two Studio windows, on one machine. Each Studio announces itself with its version and the project it has open, so an AI app can tell them apart and say which one it is working in. **Reading is always answered**, and the reply says which Studio and project it came from – so an answer about the wrong project is obvious rather than silent. **Changing anything is refused until you say which Studio you mean.** Anything that edits segments, terms, comments or files stops and lists the Studios that are open, instead of picking one. This is the point of the feature: writing into the wrong project is the one mistake you cannot see happening. **Say which one you want** and editing is enabled again for the rest of the chat: * *“Work with the 2026 one.”* * *“Use the Acme project.”* * *“Which Trados instances are running, and which are you using?”* – if you want to see the list first. The choice follows **the project, not the process**, so it survives that Studio being closed and reopened. You do not have to say it again after a restart. Closing the other Studio works just as well: the remaining one is unambiguous immediately, with nothing to restart. #### Translating two projects at once 1. Open both Studios, each with its project. 2. In the first AI app: *“Use the 2024 one”*, then set it going. 3. In the second AI app: *“Use the 2026 one”*, then set it going. Each app now edits only its own project and cannot touch the other’s document. Both can work at the same time. One assistant still works in **one** project at a time – this is two conversations running in parallel, not one assistant spanning both. #### Pinning an app to one Studio permanently If you always pair the same app with the same Studio, set it once in that app’s own MCP configuration instead of saying it each time. Add `--instance` to the server’s `args`: ```json "args": ["--instance", "2024"] ``` or set the environment variable `SUPERVERTALER_TRADOS_INSTANCE` to `2024`, `2026`, or part of a project name. A pinned app never asks – and if the Studio it wants is not running, it says so rather than quietly using the other one. #### Two chats in the same app – read this before switching windows The recipe above uses **two different AI apps** for a reason. One app runs **one** Supervertaler server, and *“Use the 2026 one”* is remembered **by that server** – not by the chat you said it in. So if you open two Claude Desktop chats, tell one *“use 2026”* and the other *“use 2024”*, and then switch between them, **both are now pointed at whichever Studio you named last.** Switching windows does not switch Studios, and the refusal above will not catch it: it only fires when *nothing* has been chosen, not when the choice is stale. This is exactly how a translation could land in the wrong project. **Give each chat one line that names its Studio, and it works only in that one.** In Claude Desktop, *Projects → Project instructions*, put in the 2026 chat’s project: > This project works only with Trados Studio 2026. Pass `instance: "2026"` on **every** Supervertaler tool call – reads as well as writes. Do **not** call `select_trados_instance`; the `instance` argument replaces it. and `"2024"` in the other. From v18.20.190 every Supervertaler tool takes an optional `instance` – `"2024"`, `"2026"`, or part of the project name – resolved against the Studios actually running. A call scoped to 2026 is answered by, or written to, the 2026 Studio and no other; one that names a Studio which is not running is **refused by name**, nothing touched. Because each call carries its own answer, the two chats never share a setting and never need `select_trados_instance` – which is the trap to avoid, since that command sets one selection shared by *every* chat, so two chats using it just overwrite each other. Pass `instance` on every call and that whole problem disappears. This is the reliable way, and it needs no second server and no file to edit. Every write also now **says which Studio and project it landed in**, in its reply, so even without the `instance` line a translation that went to the wrong place is visible at once rather than discovered later. **If you would rather it be impossible than declared** – a second server, pinned, so the two can never even see each other. Keep the extension for one Studio and add a second server for the other in `%APPDATA%\Claude\claude_desktop_config.json`: ```json { "mcpServers": { "supervertaler-2024": { "command": "C:\\Users\\\\Supervertaler\\mcp\\SupervertalerMcpServer.exe", "args": ["--instance", "2024"] } } } ``` Each chat’s instructions then name the server to use. Every tool appears twice, prefixed by server name; here that is the point, not a mistake. For most people the `instance` line above is simpler and just as safe. > The Connect dialog warns when a second Studio is running and names its project, since there is no way to tell from inside the first one. ### Direction-aware termbase writes *(from v18.20.153)* Termbases have a declared language direction, and yours don’t all point the same way – a main termbase might be en→nl while a project termbase is nl→en. From v18.20.153 `add_term` handles this per termbase: * **The AI states which language each side of the pair is in** (`sourceLang`/`targetLang`), and every termbase written to stores the pair according to **its own** declared direction. One request fills an en→nl and an nl→en termbase correctly at the same time – each entry the mirror of the other. * **Ambiguity refuses instead of guessing.** If the languages can’t be established – no document open, or a termbase whose language pair doesn’t match – the write is refused with an explanation rather than performed silently. There is deliberately no language detection: technical term pairs are routinely identical in both languages (*radar*, *transponder*), so a detector would guess, and a wrong entry that *looks* fine is worse than a refusal. * **The response proves what happened.** Every targeted termbase reports back individually: added (echoing exactly what was stored, in stored order, with a flag when the pair was reoriented), already present, or refused with the reason. `lookup_term` returns entries exactly as stored – never reoriented – and says which column your query matched, so a write can always be independently verified. * **Entries can carry their context.** `add_term` accepts a definition, domain and notes alongside the pair, and can be told to write to specific termbases only instead of all Write-enabled ones. ### Project vs background termbases *(from v18.20.159)* A common setup is two Write-enabled termbases with different roles: a large personal **background** termbase that accumulates terminology across all clients, and a per-job **project** termbase (the one with the **Project** tick in the Supervertaler Termbases settings – the same tick that renders its hits pink in TermLens). Before v18.20.159 a plain “add this term” wrote to both, indiscriminately. Now the roles are first-class: * **The AI can target a role instead of a name.** *“Add this to my project termbase”* writes only to the Project-ticked termbase; *“add this to my background termbase”* writes only to the Write-enabled ones without the tick. Job-specific decisions no longer silently pollute your general glossary. Asking for the project termbase when none is ticked is refused with an explanation, never silently redirected. * **Every result names its role.** Each termbase in an `add_term` response reports whether it is `project` or `background`, and `lookup_term` hits carry the flag too – so the AI can weight your curated project decisions above general-glossary entries when they conflict. * **Duplicates show what they matched.** When a termbase refuses a pair as already present, the response now includes the existing entry (its id and exact stored pair) instead of a bare “duplicate” – no more guessing what it collided with. * **Stale project termbases are flagged.** If the Project-ticked termbase’s name shares no word with the open project’s name – the classic sign of a tick left over from a previous job – the `add_term` response says so, before weeks of terms land in the wrong client’s termbase. ## Prompt cookbook You talk to the AI in plain language – there are no commands to memorise. The AI decides which tools to call from what you say. This section lists, per task, the kinds of things you can say, so you know the full range of what’s possible. Mix and combine freely (“find X, then fix Y”). > **Not sure where to start? Just ask *“What can I do?”*** (or *“what can you do?”*) and the assistant shows a grouped menu of everything below – so you don’t have to read this page first.  **Claude Desktop.** Ask *"What can I do?"* and the assistant lists what you can ask it, grouped by task. ### Project status and progress * “What’s the status of my Trados project?” * “How many segments are left to translate?” * “Which file am I working on, and what’s the language pair?” * “How many words are still untranslated?” / “Give me the analysis statistics – fuzzies, repetitions, new words.” *(from v18.20.95)* * “How far along is each file in this project?” *(from v18.20.95)* * “What projects do I have?” / “When did I create the ACME job, and where is it on disk?” *(all Studio versions’ registries – from v18.20.111)* * “Which TMs and project templates are on this machine?” *(from v18.20.111)* ### Finding and reading segments * “Show me all untranslated segments.” * “Show me the Draft segments so I can see what the AI wrote earlier.” * “Find all segments containing *flange*.” * “How many times does *doekrol* appear in this project? Is it translated consistently?” * “Show me segments 50 to 100.” (paging) * “List the files in this merged document.” / “Only show me segments from the contract file.” *(from v18.20.95)* ### Terminology * “What does my termbase say for *sluitkracht*?” * “Look up *support arm* – do I have an established translation?” * “Go through the project and make me a glossary of the key terms.” * “We agreed *draagarm* = *support arm* – add it to my termbase.” * “Extract the recurring technical terms from this document and add the ones I approve to my termbase.” * “That pair is outdated – replace it with the official MDR term in both termbases.” *(update, exact-match, audited in chat – from v18.20.113)* * “Delete that junk entry the QA keeps flagging.” *(Write-enabled termbases only; the AI confirms before deleting – from v18.20.113)* * “Only consult my **active** termbases for this lookup.” *(restricts to termbases with Read ticked; otherwise inactive hits are flagged – from v18.20.113)* * “Add *commandovoering* = *command and control* to my termbases – with the NATO definition and a usage note.” *(direction-aware per termbase, with definition/domain/notes – from v18.20.153)* * “Add this pair to the Acme termbase only.” *(write to named termbases instead of all Write-enabled ones – from v18.20.153)* * “Add this to my **project** termbase only.” / “Put that one in my **background** termbase, it’s not client-specific.” *(role-based targeting via the Project tick – from v18.20.159)* * “Extend the usage note on *eenzelfde* with a warning about the split spelling.” *(edit an entry’s notes, definition or domain in place, without touching the pair – from v18.20.159)* ### Translation memory * “How did I translate this sentence before?” *(searches the Trados TMs attached to your project – from v18.20.95)* * “Search my TM for *scherminrichting*.” * “Search only the target side of my TMs for *roller blind*.” *(from v18.20.95)* * “Before translating, check my TM and termbase and follow what you find.” ### The segment I’m working on * “Translate this segment.” / “Explain this sentence.” * “What do my TM and termbase say about the current segment?” * “Give me three alternative translations for this segment, then insert the one I pick.” ### Writing translations (always reviewable) * “Draft translations for all untranslated segments – I’ll review them in Studio.” * “Translate the segments containing *warranty*, use my termbase, set them to Draft.” * “Redo segment 14 – too literal, make it flow better, then update it.” * “Set all my Draft segments to Translated.” (status-only changes work too) Everything the AI writes lands as **Draft** unless you say otherwise, locked segments are never touched, and nothing is saved until you save in Studio. ### Quality and consistency * “Find segments where the source and target numbers don’t match.” *(from v18.20.95)* * “Check my tags – any segments missing formatting?” *(from v18.20.95)* * “Check my translated segments against the termbase and list violations.” *(from v18.20.95)* * “Find all repeated sentences that I translated differently.” *(from v18.20.95)* * “Check whether I’ve lost any non-breaking spaces.” *(from v18.20.148)* * “Put a non-breaking space between every value and its unit.” *(from v18.20.148)* * “Where does my translation differ from the client’s reference TM?” *(from v18.20.148)* * “Run all your QA checks and give me a report.” * “…then align them all to the best version.” (pairs with the write tools) Comparing against the TM is worth a note of its own, because it answers a different question from concordance search. Searching the TM tells you whether a phrase *you already suspect* was translated before – one query at a time, for things you thought to look up. `compare_document_to_tm` goes the other way: it reads the attached TMs once and checks **every** segment whose source appears in them, then reports only where your wording differs. That surfaces the cases you had no reason to check, which is exactly where an established client rendering gets missed. Two things to keep in mind. A difference is not automatically a mistake – on a real job most of them are deliberate improvements, and an improvement is indistinguishable from an error here, so the assistant is instructed to present the list for you to judge rather than align anything itself. And only segments whose source matches the TM word for word are compared, so a clean result means “nothing contradicts the TM”, not “the whole document agrees with it”. Non-breaking spaces deserve a note of their own. They are invisible everywhere – in Studio, in the AI’s view of your segments, in any report – so a lost one usually surfaces only when the client rejects the file. That matters if your style guide asks for one between a value and its unit (230 V, 3,5 mm, 50 %) or before a figure reference. `check_nbsp` compares each translated segment against its source and lists the ones that came out with fewer. Inserting them used to be the harder half. A non-breaking space typed straight into a tool call survives the trip only sometimes: depending on the AI client and the individual call, it either arrives intact or is normalised to an ordinary space on the way, and because the write itself succeeds, nothing tells you which happened. Escape codes don’t help either – the AI client decodes them into the character first, and then the character is what gets flattened. Being intermittent makes it worse rather than better: it works when you try it, and fails on the job. From v18.20.148 the AI can write the character as the HTML entity ` `, which Supervertaler turns into a real non-breaking space at the Trados end. Plain ASCII travels intact, so nothing en route can mangle it. This works for both writing translations and find & replace, and searching, so *“put a non-breaking space between every value and its unit”* fixes a whole document in one pass – and because find & replace preserves confirmation status, doing that to a finished file leaves it finished. It is deliberately opt-in, so a document that genuinely contains the text ` ` (an HTML manual, say) is never silently rewritten. ### Resources * “Which TMs and termbases is this project using?” *(from v18.20.95)* * “Are any of my termbases actually switched on for this project?” *(from v18.20.148)* – termbases are enabled per project, so a project with all of them off looks exactly like one with no terminology at all. The AI is now warned when nothing is read-enabled instead of silently finding no terms. ### Your memory bank *(from v18.20.146)* Your [SuperMemory](/trados/ai-assistant/super-memory/) memory bank holds the reasoning behind your decisions – why a term was chosen, what a client insists on, what you rejected last time – which is exactly what a TM or termbase cannot tell an AI. From this version the AI can read it over MCP, not just inside the Supervertaler chat panel: * “Read my memory bank for this project before we start.” * “What did I decide about *inrichting* for this client, and why?” * “Check this translation against my style guide and terminology notes.” * “Which memory bank are you using?” The AI cites the articles it drew from by path, so you can open them in Obsidian and check its reasoning. Retrieval is read-only – nothing is written back to the bank over MCP. If you have turned memory-bank context off under Settings → AI Settings, these tools stay quiet too. A large bank will not fit into one answer, so some of it is left out – and **the AI is now told which files those were** *(from v18.20.183)*. It used to be trimmed silently, which is the worse failure: two of your three articles look exactly like all three, so a rule you had written down could be absent from the answer with nothing to say so. If the AI mentions that something was left out, ask it to read the bank again with a larger budget, or ask about that file by name. ### Your prompt library *(from v18.20.101)* The AI can read and improve the Markdown prompts in your Supervertaler prompt library – the same ones you use in the QuickLauncher and Batch Translate (and shared with Supervertaler for memoQ): * “List my prompts.” / “Show me the prompts in my Translate folder.” * “Show me my Default Translation Prompt.” * “Look at my Default Translation Prompt and suggest improvements for patent work, then save it as a new prompt.” * “Turn what we just worked out into a prompt and save it as *Client X house style*.” * “Look at my open project and write me a translation prompt tailored to it.” *(from v18.20.109 – the AI reads the source text, detected domain, relevant terms, and TM examples via `get_prompt_context`, then drafts and saves the prompt. How much source it sees is set under Settings → AI Settings → “Prompt context – source segments”; 0 = the whole document.)* Built-in default prompts are protected – the AI saves your version under a new name rather than overwriting them. ### Working across sources Because the AI has all tools in one conversation, the most powerful prompts combine them: * “Compare how I translated *closing force* in this project vs my TM – if they differ, tell me which is more common and align the project.” * “Draft the remaining segments, but first build a glossary from the segments I already translated and stick to it.” * “Review my Draft segments against the source: flag mistranslations, fix typos directly, and list anything you weren’t sure about.” Given a long enough task, an assistant will keep going on its own:  **ChatGPT desktop.** Asked to carry on unattended, reporting back on a 1,064-segment file it translated, proofread and saved through the MCP server. Everything it did landed in Trados Studio, where it can be reviewed segment by segment like any other work. Worth knowing before trying it: the assistant writes into your project as it goes, so review the result as you would a colleague’s draft – the confirmation status it leaves, and Trados’s own verification, are what make that practical. An unattended run also spends tokens without you watching, so set a budget you are comfortable with first. Version tags like *(from v18.20.111)* show the plugin version a capability first shipped in – if the AI doesn’t offer it, update the plugin. New tools appear in your AI app automatically after a plugin update; no extension reinstall is needed. ## Setting it up  The External AI assistants (MCP) section at the bottom of the AI Settings tab. 1. In Trados Studio, open **Supervertaler Settings → AI Settings** and click **Connect AI assistant…** at the bottom. The dialog shows your current connection status. 2. **Claude Desktop** (easiest): click **Download extension (.mcpb)** to get `Supervertaler-MCP-Server.mcpb`. Then in Claude Desktop open **Settings → Extensions** and **drag the `.mcpb` file onto the page** – it shows a *“Drag .MCPB or .DXT files here to install”* target. (Prefer a file picker? Scroll to **Advanced settings** and use the **Install extension…** button instead.) Confirm the install. Double-clicking the `.mcpb` only works if your system has associated that file type with Claude Desktop; many don’t and will ask which app to use – just cancel and drag-and-drop instead. 3. **ChatGPT desktop** *(Windows)*: ChatGPT desktop can run the server, but it has no drag-and-drop installer, so this is a short manual step. It takes about two minutes. **a. Get the server.** In the **Connect AI assistant…** dialog click **Download server (.zip)** (or take `Supervertaler-MCP-Server-exe.zip` from any [GitHub release](https://github.com/Supervertaler/Supervertaler-for-Trados/releases/latest)). Unzip it and move `SupervertalerMcpServer.exe` somewhere **permanent** – for example `C:\Users\\Supervertaler\mcp\`. Do not leave it in Downloads: the path goes into a config file, and moving or clearing the file later breaks the connection. **b. Open the config file.** ChatGPT desktop reads its MCP servers from the same file as Codex CLI: ```plaintext %UserProfile%\.codex\config.toml ``` Paste that path into File Explorer’s address bar to jump straight to the folder. If the file or the `.codex` folder does not exist yet, create them – a config with only the block below in it is perfectly valid. **c. Add the server.** Append this to the end of the file, replacing the path with where you actually put the exe: ```toml [mcp_servers.supervertaler] type = "stdio" command = 'C:\Users\\Supervertaler\mcp\SupervertalerMcpServer.exe' args = [] enabled = true ``` Use **single quotes** around the path, as shown. In TOML that makes it a literal string, so Windows backslashes are taken exactly as typed. With double quotes you would have to write every backslash twice. **d. Restart ChatGPT desktop properly.** Closing the window is not enough – it keeps running in the notification area. Right-click its icon there and quit, then start it again. **e. Check it.** With Trados Studio running, ask ChatGPT: *“What Trados project is open?”* It should name your project, and `SupervertalerMcpServer` should appear under **Sources** in the reply. > **If nothing happens**, work through these in order: is Trados Studio actually running? Does the path in `config.toml` point at a file that exists? Did you fully quit ChatGPT from the notification area? And is the rest of the file still valid TOML – a stray character anywhere in it can stop *every* server loading, not just this one. 4. **Mistral Vibe CLI** *(Windows)*: Vibe is Mistral’s terminal coding agent – the CLI half of the product that used to be called le Chat. It runs local STDIO servers, so it can drive Trados just as Claude Code does. Worth knowing about if you need an EU-based, GDPR-compliant provider, or want to work on Mistral’s free tier. You chat in a terminal window rather than a polished desktop app; there is no Mistral desktop client, and Vibe’s *web* connectors are remote-only, so the CLI (or Vibe inside VS Code, JetBrains or Zed) is the only route to a local server. **a. Get the server.** Exactly as in step 3a above – **Download server (.zip)**, unzip it, and put `SupervertalerMcpServer.exe` somewhere permanent. **b. Add it to `config.toml`.** Vibe keeps its settings in: ```plaintext %UserProfile%\.vibe\config.toml ``` Append this, replacing the path with your own: ```toml [[mcp_servers]] name = "supervertaler" transport = "stdio" command = ['C:\Users\\Supervertaler\mcp\SupervertalerMcpServer.exe'] args = [] startup_timeout_sec = 30.0 tool_timeout_sec = 300.0 ``` Note the shape of `command`: **square brackets around a single-quoted path**. This one detail is what most Windows setups get wrong, and it fails in a confusing way – see the box below. Note also the double square brackets on `[[mcp_servers]]`; Vibe’s server list is a TOML array of tables, not a single table like ChatGPT’s. > **Why the brackets matter.** If you give `command` as a plain string, Vibe splits it with POSIX shell rules, which treat `\` as an escape character – so `C:\Users\you\...` silently becomes `C:Usersyou...`, a path that doesn’t exist. The server then never starts, and Vibe shows a connection error that does not go away. Wrapping the path in `[ ]` makes it a ready-made argument list that skips the splitting entirely. Writing the path with forward slashes (`C:/Users/you/...`) works too, and Windows accepts it. > > The same applies to `vibe mcp add … --command …`, which stores the path as a string: on Windows, prefer editing `config.toml` by hand. **c. Why the two timeouts.** Vibe defaults to a 10-second server start-up limit and a 60-second cap per tool call. Trados can take longer than that to answer while a project is loading, and the long-running tools (pre-translation, verification, comparing a document against a TM) routinely exceed a minute. The values above give them room; the bridge’s own limit is 5 minutes. **d. Check it.** Start Trados Studio **first**, then run `vibe` and type `/mcp` (or `/connectors`). Your server should be listed; `/mcp supervertaler` lists the tools it exposes. Then ask: *“What Trados project is open?”* 5. **Google Antigravity** *(confirmed September 2026)*: Antigravity is Google’s agentic desktop app – the Google-side counterpart to Claude Desktop and ChatGPT desktop, and the route to driving Trados from Gemini with a real interface rather than a terminal. > **Not Gemini Code Assist in VS Code.** Google has retired the free Gemini Code Assist tier for individuals in the VS Code extension. Signing in now returns *“This client is no longer supported for Gemini Code Assist for individuals”* and points you at Antigravity. Don’t spend time on that route. **a. Get Antigravity.** Download it from [antigravity.google/download](https://antigravity.google/download) and sign in with a **personal Google account**. A paid Google **Workspace** account – your own domain – is refused: Google restricts the free tier to consumer accounts, and a Workspace sign-in fails with a licence error. (During onboarding you’re offered “Build with Google” plugins for Firebase, Flutter, Maps and so on. None are relevant to translation work; leave them all unticked, as each adds its own tools alongside Supervertaler’s.) **b. Get the server.** Exactly as in step 3a – **Download server (.zip)**, unzip it, and put `SupervertalerMcpServer.exe` somewhere permanent. **c. Add the server.** Open **Settings → Customizations**, scroll to **Installed MCP Servers**, and click **Add MCP**. Or edit the config file directly – **Open MCP Config** in that same panel takes you to it: ```plaintext %UserProfile%\.gemini\config\mcp_config.json ``` ```json { "mcpServers": { "supervertaler": { "command": "C:\\Users\\\\Supervertaler\\mcp\\SupervertalerMcpServer.exe", "args": [] } } } ``` JSON requires every backslash to be doubled, as shown – or write the path with forward slashes, which Windows also accepts. Quit Antigravity completely afterwards and start it again; the file is read at startup. **d. Check it.** **Settings → Customizations → Installed MCP Servers** should list `supervertaler` with a green dot and a tool count – *“51 tools enabled”* at the time of writing, more as the plugin gains tools. Expand it to see the tool names. Then, with Trados Studio running, ask: *“What Trados project is open?”* > **Don’t test it by asking the AI to list its MCP tools.** It will tell you, confidently, that it has none – even with every tool connected and working. Models are unreliable about their own toolset. Trust the Settings panel and a real question instead. **e. Teach it to use the tools.** This step matters more here than with any other client. Antigravity’s agent has a shell and a file browser, and left to itself it will try to answer Trados questions by digging through `projects.xml` and your project folder – slowly, and from stale data, because neither reflects what Studio currently has open. On one 675-segment project that meant eight minutes, thirteen shell commands and no answer; the same question with the tools named took fourteen seconds. Supervertaler ships the instruction file that fixes this. In Trados, open **Supervertaler Settings → AI Settings → Connect AI assistant…**, scroll to **Google Antigravity**, and click **Install Antigravity skill**. It writes: ```plaintext %UserProfile%\.gemini\config\skills\supervertaler-trados\SKILL.md ``` Then restart Antigravity and check **Settings → Customizations** – it appears as `supervertaler-trados`, tagged `Global`. Start a **new conversation**; one already running keeps the instructions it began with. The Gemini CLI reads the same folder, so it is covered by the same click. The skill tells the agent to load your recorded decisions first, then run the `check_*` tools, then read the bilingual text – and not to write scripts to do any of it. Because it ships with the plugin it stays current: it names specific tools and rules, and a copy pasted by hand would slowly start describing a toolset that no longer matches. If you have edited your own copy, the button backs it up before replacing it. > **Gemini CLI** (terminal, no interface) reads a *different* file. Register the server with `gemini mcp add supervertaler --scope user "C:\Users\\Supervertaler\mcp\SupervertalerMcpServer.exe"`, which writes to `%UserProfile%\.gemini\settings.json`. Watch for its folder-trust gate: in a folder you haven’t trusted it disables every MCP server – including user-scope ones – and says so when you run `gemini mcp list`. 6. **Other MCP clients (Claude Code, etc.)**: click **Copy config snippet** and paste it into the app’s MCP configuration, adjusting the path to where you saved `SupervertalerMcpServer.exe`. The snippet is in Claude’s JSON format; clients that use a different format need the same two facts – the transport is STDIO, and the command is the path to that exe. Then open a project document in the Trados editor, and ask your AI app: *“What’s the status of my Trados project?”* > **Tip.** The connection starts automatically **as soon as Trados Studio is running** – no document or panel needed, so machine-wide questions (“what projects do I have?”) work straight from the Projects view. (History: on 18.20.99–18.20.111 the connection started when you opened a document in the editor; before 18.20.99 you had to click the Supervertaler Assistant panel once per session.) Install the extension **or** use a manual config entry – not both, or every tool will appear twice in the AI app. The Connect dialog warns you if it detects this. ## Privacy and security Everything stays on your computer: * The connection between the AI app and Trados runs over **localhost only** – nothing is exposed to your network or the internet. * Every Trados session uses a **fresh access token**; only programs on your own machine that hold the token can connect. * Your project data goes to an AI model only when *you* ask the AI a question about it, through the AI app you chose – exactly as if you had pasted the text yourself. The MCP server itself sends nothing anywhere. ## Requirements * Supervertaler for Trados with an active licence or trial (the bridge is part of the AI Assistant). * An MCP client that runs local STDIO servers on your own machine: Claude Desktop (recommended, one-click install), ChatGPT desktop, Google Antigravity, Claude Code, Gemini CLI, Mistral Vibe CLI, or similar. This means an app that executes the server **on your PC** – the claude.ai and chatgpt.com *websites*, and Mistral’s Vibe web app, all run servers in the cloud and cannot reach a local one. * Windows (the MCP server is a self-contained exe; no additional runtimes needed). ## Keeping it up to date **The MCP server is a separate component and does not update with the plugin.** Updating Supervertaler for Trados through the App Store updates the half that lives inside Studio; the `.mcpb` extension (or the unzipped exe) is installed in your AI app and stays exactly as it was until you replace it. The two halves talking to each other across a version gap is the single most common source of odd behaviour. After a plugin update that mentions the MCP server in its release notes, reinstall the extension: download the current `.mcpb` from the [latest release](https://github.com/Supervertaler/Supervertaler-for-Trados/releases/latest), install it the same way you did the first time, and restart your AI app. Installing over the existing extension is enough; there is nothing to uninstall first. Good news first: **the list of tools is not baked into it.** The server asks Studio for the current tool list every time it starts, so tools and options added by a plugin update work with an older server – provided Studio was running when your AI app started. What *is* fixed at install time is the server’s own behaviour, and the one symptom worth recognising is: * **Errors mentioning a timeout of 30 seconds.** That limit was raised to 5 minutes in v18.20.148, so if you still see it, the installed server predates that release and should be replaced. ## Troubleshooting * **The AI doesn’t know about a tool or option the release notes describe** – this is almost never a stale download. The tool list is read from Studio once, when your AI app starts, and kept for that whole session, so an option added by a plugin update is missing simply because the AI app was already running (or started while Studio was closed) – a new option is then dropped from the call silently rather than reported as an error. The fix is order, not reinstallation: **start Trados Studio first, then start (or fully restart) your AI app.** * **Double-clicking the `.mcpb` file asks which app to open it with** – your system has no `.mcpb` association. Cancel the dialog and instead either **drag the `.mcpb` onto the Extensions page**, or use Claude Desktop’s **Settings → Extensions → Advanced settings → Install extension…** button. (Drag-and-drop works once the Extensions page has finished loading – if it’s stuck on “Loading extensions…”, see the next point first.) * **The Extensions page is stuck on “Loading extensions…”** – the page needs to reach Anthropic’s extension directory once before it renders; we’ve seen it hang on the Microsoft Store build of Claude Desktop. Fully quit Claude Desktop (including the system tray icon) and reopen it; check your internet connection. If it keeps hanging, there’s a universal fallback that skips the Extensions page entirely: download `Supervertaler-MCP-Server-exe.zip` instead, unzip it somewhere permanent, and use the **Copy config snippet** button in the plugin’s Connect dialog to add the server manually to `claude_desktop_config.json` (Claude Desktop → Settings → Developer → Edit Config). * **The AI says it can’t reach Trados** – make sure Trados Studio is running; from v18.20.112 the connection starts with Studio itself (on 18.20.99–18.20.111 you additionally needed a document open in the editor, and before that a click on the Supervertaler Assistant panel – updating the plugin removes those steps). The Connect dialog’s status lines show whether the connection is up. Tools that read the open document still need one open, and will say so. * **Tools appear twice in Claude Desktop** – you have both the extension and a manual config entry; remove one (see above). * **Mistral Vibe CLI shows a permanent “cannot connect” message, but `/mcp` lists the server as enabled** – `/mcp` reports what is *configured*, not what is *connected*, so the two are not in conflict: the banner is right and the server really did fail to start. On Windows the usual cause is the path in `command` being written as a plain string, which Vibe splits with POSIX rules and strips the backslashes from. Put the path in square brackets, or use forward slashes – see step 4 of [Setting it up](#setting-it-up). A second, milder cause is Vibe’s 10-second start-up limit expiring while Studio is still busy; raise `startup_timeout_sec`. * **The AI refuses to change segments and mentions two instances** – you have both Studio 2024 and Studio 2026 open, and it will not guess which one you mean. Tell it (*“use the 2026 one”*), or close the Studio you are not working in. Reading still works throughout. See [Two Studios open at once](#two-studios-open-at-once-from-v1820184). * **Term lookups return nothing** – check that your termbase/database path is set correctly in the Supervertaler settings (the same path TermLens uses). * The bridge writes a diagnostic log to `\trados\runtime\bridge.log`. Development of this feature is tracked publicly in [issue #44](https://github.com/Supervertaler/Supervertaler-for-Trados/issues/44) – feedback and use-case ideas are very welcome. # MultiTerm Support TermLens automatically detects MultiTerm termbases (`.sdltb` files) attached to your active Trados project and displays their terms alongside your Supervertaler terms. ### How It Works When you open a project in Trados Studio that has MultiTerm termbases attached, TermLens reads those `.sdltb` files and loads all term pairs into its matching engine. MultiTerm terms appear as **green chips** in the TermLens panel, right next to the blue, pink, and yellow chips from your Supervertaler termbases. There is nothing to configure. If your Trados project has MultiTerm termbases attached and **enabled** (via **Project Settings > Language Pairs > Termbases**), TermLens picks them up automatically. Termbases with the **Enabled** checkbox unchecked in Trados are ignored. #### Colour coding | Colour | Meaning | | ------------ | ---------------------------------------------------- | | **Blue** | Regular Supervertaler termbase match | | **Pink** | Project termbase match (higher priority) | | **Yellow** | Non-translatable term (source = target) | | **Green** | MultiTerm termbase match (`.sdltb`) | | **Lavender** | Abbreviation match (matched via source abbreviation) | Green chips behave like any other TermLens chip – click to insert, or use **Alt+1** through **Alt+9** to insert by number. ![]() ### Read-Only MultiTerm termbases are **read-only** in TermLens. You cannot add, edit, or delete terms in a MultiTerm termbase from the TermLens panel. To manage MultiTerm terms, use Trados Studio’s built-in MultiTerm interface. When you right-click a green MultiTerm chip, the Edit, Delete, and “Mark as Non-Translatable” options are not shown. ### Auto-Refresh TermLens monitors your MultiTerm termbases for changes: * **Term changes** –when you add or edit terms using Trados’s native MultiTerm interface, TermLens detects the file change on the next segment navigation and reloads automatically. * **Config changes** –when you enable or disable a MultiTerm termbase in **Project Settings > Termbases**, TermLens detects the change within a few seconds and updates the panel automatically – no segment change needed. ### MultiTerm Termbases in Settings MultiTerm termbases appear at the bottom of the termbase list in the **Supervertaler Settings** dialogue (gear icon > TermLens tab). Each one is labelled with **\[MultiTerm]** and has a light green background to distinguish it from Supervertaler termbases. | Toggle | Behaviour | | ----------- | ------------------------------------------------------------------------------ | | **Read** | Controls whether this termbase’s terms appear in TermLens. Uncheck to hide it. | | **Write** | Always disabled –MultiTerm termbases are read-only in TermLens | | **Project** | Always disabled –only Supervertaler termbases can be the project termbase | To add or remove MultiTerm termbases from your project, use Trados Studio’s **Project Settings > Language Pairs > Termbases**. ### MultiTerm and AI Terminology Injection Your MultiTerm termbases are loaded and used for **AI terminology injection**. This means the AI Assistant, Batch Translate, and Ctrl+T all receive your MultiTerm terminology in their prompts, helping the AI use the correct approved terms – as long as the termbases are enabled in Trados Project Settings. ### Technical Details TermLens reads `.sdltb` files directly using the JET 4.0 database driver built into Windows. This is the same driver that MultiTerm itself uses. If the JET driver is not available (uncommon on modern Windows), TermLens falls back to Trados’s terminology provider API for per-segment lookups. Because the access is read-only, there is no risk of data corruption. TermLens opens the `.sdltb` file in shared read mode, so MultiTerm and Trados can continue to use it simultaneously. ### Troubleshooting #### MultiTerm terms not appearing 1. **Check the Trados Enabled checkbox** –open **Project Settings > Language Pairs > Termbases** and make sure the termbase’s **Enabled** checkbox is ticked 2. **Check the Read toggle** –open Supervertaler Settings and make sure the MultiTerm termbase’s Read checkbox is enabled 3. **Check languages** –the termbase’s source and target languages must match the current project’s language pair #### Terms added in MultiTerm not updating * Navigate to a different segment –this triggers the auto-refresh check * If terms still do not appear, close and reopen the settings dialogue to force a full termbase reload *** ### See Also * [TermLens](/trados/termlens/) * [Termbase Management](/trados/termbase-management/) * [TermLens Settings](/trados/settings/termlens/) * [Troubleshooting](/trados/troubleshooting/) # Privacy For the full Supervertaler privacy policy, please visit: **[supervertaler.com/privacy](https://supervertaler.com/privacy/)** ## Summary * Supervertaler does **not** collect, store, or transmit your translations, termbases, or documents to Supervertaler servers * Your translations, termbases, and documents stay on your machine * When you use AI features, data is sent directly to the AI provider **you** selected, using your own API key * **Optional anonymous usage statistics** – strictly opt-in. If you consent, a single ping on startup sends only: plugin version, OS version, Trados version, and system locale. No personal data, no translation content. You can opt out at any time in Settings. See [Usage Statistics](/trados/settings/usage-statistics/) for full details. * **Trial registration** (v18/19.20.118+) – trial installs register the trial’s start date with a first-party licence endpoint on startup, so the trial behaves consistently across reinstalls. Only the anonymous machine hash, plugin/Studio version, locale, and the trial’s start date are sent – no content, no personal data. This is part of how the trial functions (like licence validation) and is separate from the opt-in usage statistics. See the [full privacy policy](https://supervertaler.com/privacy/) for details. * For maximum confidentiality with AI features, use [Ollama](https://ollama.com) – all processing stays local * Source code is publicly available on [GitHub](https://github.com/Supervertaler/Supervertaler-for-Trados) for independent verification ## Contact Questions about privacy? Email . # QuickLauncher QuickLauncher gives you one-click access to your most-used AI prompts directly from the Trados editor, without switching panels or typing anything. ### How it works 1. **Right-click** anywhere in the editor (or press `Alt+Q`) 2. Click **QuickLauncher** in the context menu 3. Select a prompt from the list 4. The prompt is filled in with the current segment context and submitted to the Supervertaler Assistant chat  The QuickLauncher context menu with folder sections and keyboard shortcuts. The expanded prompt appears as a user message bubble in the **Supervertaler** chat panel, and the AI response follows immediately below it. The conversation continues from there – you can ask follow-up questions in the chat input as normal. ### QuickLauncher vs Translate Active Segment (Alt+T) These are two different pipelines, and the difference matters: * **Translate active segment (`Alt+T`)** runs through the **Batch Translate pipeline**: it uses the prompt currently selected in the Batch Translate tab, plus the same provider, termbase terms, document context and SuperMemory context as a batch run, and writes the result straight into the target cell. *(Document and SuperMemory context from v18/19.20.149 – before that, single segments were sent without context, which made them translate noticeably worse than a batch.)* * **QuickLauncher** runs through the **Assistant chat**: it fills in whichever prompt template you assigned to the slot and shows the answer in the chat panel. What context the AI sees depends entirely on the template – surrounding text only if it contains `{{SURROUNDING_SEGMENTS}}`, the whole document only if it contains `{{PROJECT}}`, and so on (see the variables below). If your goal is simply *“translate this segment the way a batch would”*, use `Alt+T`. Use QuickLauncher when you want a custom prompt’s behaviour – explaining a term, assessing a translation, or translating with special instructions of your own. ### Keyboard shortcut | Shortcut (Windows) | Shortcut (Mac) | Action | | ------------------ | -------------- | ------------------------------ | | `Alt+Q` | `Option+Q` | Open QuickLauncher prompt menu | ### Prompt variables QuickLauncher prompts have access to the full segment and project context at the moment you trigger them. #### Language variables | Variable | Replaced with | Example | | --------------------- | -------------------------------------- | ------------------------- | | `{{SOURCE_LANGUAGE}}` | Source language name, including locale | `Dutch (Belgium)` | | `{{TARGET_LANGUAGE}}` | Target language name, including locale | `English (United States)` | #### Segment variables | Variable | Replaced with | Example | | -------------------- | -------------------------------------------------------------------- | -------------------------------------- | | `{{SOURCE_SEGMENT}}` | Full text of the **active source segment** | `De uitvinding heeft betrekking op...` | | `{{TARGET_SEGMENT}}` | Full text of the **active target segment** (your translation so far) | `The invention relates to...` | | `{{SELECTION}}` | Text currently **selected** in the editor | `werkwijze` | #### Project variables | Variable | Replaced with | | -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- | | `{{PROJECT_NAME}}` | Trados project name (e.g. `Patent_NL_EN_2026`) | | `{{DOCUMENT_NAME}}` | Active file name (e.g. `source_document.docx`) | | `{{SURROUNDING_SEGMENTS}}` | N source segments before and after the active segment, with their actual Trados segment numbers and the active segment marked `← ACTIVE` | | `{{PROJECT}}` | All source segments in the active document, numbered with their actual Trados segment numbers | | `{{TM_MATCHES}}` | Translation memory fuzzy matches (≥70%) for the active segment, showing match percentage, source, and target text | **`{{SURROUNDING_SEGMENTS}}` example output** (with N = 2): ```plaintext [11] Vorige zin hier. [12] Nog een vorige zin. [13 ← ACTIVE] De uitvinding heeft betrekking op een nieuwe werkwijze... [14] Volgende zin hier. [15] Nog een volgende zin. ``` **`{{PROJECT}}` example output** (single-file project): ```plaintext [1] De uitvinding heeft betrekking op een nieuwe werkwijze... [2] De conclusies omvatten de volgende kenmerken... [3] ... ``` In a **multi-file project**, a file header is inserted at each boundary (because Trados restarts segment numbering per file): ```plaintext === File 1 === [1] Conclusie 1 omvat... [2] Conclusie 2 omvat... === File 2 === [1] De beschrijving begint hier... ``` Caution `{{PROJECT}}` sends all source segments to the AI. For a typical 10,000-word patent this costs roughly **4–5 cents** per call with a Sonnet-class model – negligible for important work, but avoid using it in high-frequency prompts. The number of surrounding segments for `{{SURROUNDING_SEGMENTS}}` is configured in **Settings → AI Settings → Surrounding segments** (default: 5). To keep the chat history readable, the chat bubble shows a compact summary (e.g. `[source document – 47 segments]`) instead of the full source text. The complete document is still sent to the AI. #### Example: explain a selected term Select a word in the source segment, press `Alt+Q`, and choose a prompt like this: ```plaintext The user is translating from {{SOURCE_LANGUAGE}} to {{TARGET_LANGUAGE}}. The selected term is: {{SELECTION}} Explain what this term means and suggest the best {{TARGET_LANGUAGE}} equivalent, considering the full segment context below: {{SOURCE_SEGMENT}} ``` #### Example: assess the current translation ```plaintext Source ({{SOURCE_LANGUAGE}}): {{SOURCE_SEGMENT}} My translation ({{TARGET_LANGUAGE}}): {{TARGET_SEGMENT}} Assess how I translated the current segment. Point out any inaccuracies, awkward phrasing, or terminology issues, and suggest improvements. ``` #### Example: translate a selected term using surrounding context Uses `{{SELECTION}}` together with `{{SURROUNDING_SEGMENTS}}` so the AI sees the passage around the active segment, not just the active segment itself: ```plaintext I am translating a {{SOURCE_LANGUAGE}} patent into {{TARGET_LANGUAGE}}. The selected term is: {{SELECTION}} Here is the passage surrounding the active segment for context: {{SURROUNDING_SEGMENTS}} Suggest the best {{TARGET_LANGUAGE}} translation for "{{SELECTION}}" given the surrounding context. Give a brief explanation of your reasoning. ``` #### Example: full-document term query Uses `{{PROJECT}}` to give the AI the complete source text. Reserve this for high-stakes queries where full document context matters, such as a key term that appears in multiple places with different nuances: ```plaintext I am translating a {{SOURCE_LANGUAGE}} patent ({{DOCUMENT_NAME}}) into {{TARGET_LANGUAGE}}. Project: {{PROJECT_NAME}} Here is the complete source text, segment by segment: {{PROJECT}} Throughout this document, what is the most accurate and consistent {{TARGET_LANGUAGE}} translation for "{{SELECTION}}"? Consider all occurrences in context and note any variation in meaning between them. ``` #### Example: check specific segments by number After using `{{PROJECT}}` the AI knows the segment numbers, so you can follow up in the chat – or build a prompt that asks about specific segments from the start: ```plaintext I am translating a {{SOURCE_LANGUAGE}} patent into {{TARGET_LANGUAGE}}. Here is the source document: {{PROJECT}} My translations so far: - Segment 1: [paste your translation here] - Segment 4: [paste your translation here] Do you think these translations are accurate and consistent with the terminology used elsewhere in the document? ``` #### Example: translate using TM fuzzy matches Uses `{{TM_MATCHES}}` to give the AI any high fuzzy matches from the translation memory, so it can leverage existing translations as a starting point: ```plaintext Translate the following segment from {{SOURCE_LANGUAGE}} to {{TARGET_LANGUAGE}}. Source: {{SOURCE_SEGMENT}} Here are fuzzy matches from my translation memory: {{TM_MATCHES}} Use the fuzzy matches as reference where helpful, but produce an accurate translation of the source segment – do not simply copy a fuzzy match. ``` The plugin fills in all variables and sends the expanded prompt straight to the AI. ### Folder display mode By default, subfolders in the QuickLauncher menu appear as **expandable submenus** (hover to open). You can change any folder to display as a **flat section** instead – its prompts appear directly in the main menu under a bold header, with separators between sections. To toggle the display mode: 1. Open **Settings → Prompts** 2. Right-click a QuickLauncher folder in the tree 3. Click **Show as section in menu** (a checkmark indicates the current state) This setting is per-folder, so you can mix styles – for example, keep a large folder as an expandable submenu while showing a small one as a flat section. ### Setting up QuickLauncher prompts Set `category: QuickLauncher` in the YAML frontmatter, or place the file in a folder called `QuickLauncher` inside your `prompt_library`. See [Prompts → Marking a prompt as a QuickLauncher shortcut](/trados/settings/prompts/#marking-a-prompt-as-a-quicklauncher-shortcut) for full details. ### Shared with Supervertaler for memoQ QuickLauncher prompts live in the shared `prompt_library` folder used by both Supervertaler for Trados and Supervertaler for memoQ. Any prompt you create in one application is immediately available in the other. #### YAML reference If you prefer editing prompt files directly, the relevant frontmatter fields are: ```yaml --- name: Explain selected term category: QuickLauncher quicklauncher_modes: [assistant, clipboard] default_mode: assistant --- ``` * `quicklauncher_modes:` – accepts an inline list `[assistant, clipboard]` or a comma-separated string `assistant, clipboard`. Unknown values are silently dropped. When omitted, defaults to `[assistant]`. * `default_mode:` – which mode appears first in the submenu when both are configured. Must be one of the values in `quicklauncher_modes`. Defaults to `assistant`. *** ### See Also * [Text Transforms](/trados/text-transforms/) * [Prompts](/trados/settings/prompts/) * [Supervertaler](/trados/ai-assistant/) * [Keyboard Shortcuts](/trados/keyboard-shortcuts/) # Reports The **Reports** tab in the Supervertaler Assistant panel is where the assistant collects structured output from its AI operations. Two kinds of thing land here: **proofreading results** and an optional **log of AI calls**. ## Proofreading results When you run the **AI Proofreader** (the Proofread mode of [Batch Operations](/trados/batch-operations/)), each issue the AI finds is shown here as a clickable card. See [AI Proofreader](/trados/ai-proofreader/) for the full workflow and what each card contains. Since v18.20.187 every completed run is also written to `trados\ eports` in your data folder as Markdown, and **Save report…** next to **Clear** writes a copy wherever you choose. The button is enabled only while a proofreading report is showing. ## AI operation log When **Log prompts and responses to Reports tab** is enabled in [AI Settings](/trados/settings/ai-settings/), AI calls – Chat, Batch Translate, Batch Proofread and AutoPrompt – are recorded here together with the prompt, the response, the model used and the token/cost figures. It is the place to audit exactly what was sent to the AI provider and to review cost after the fact. # Ai Settings Configure the AI provider, model, and context options used by the Supervertaler for Trados plugin. ## Accessing AI settings Open the plugin **Settings** dialogue and switch to the **AI** tab. ## Provider selection Choose one of the supported AI providers: | Provider | Models | Where to get a key | | ------------------------------ | ------------------------------------------------------------------ | -------------------------------------------------------------------- | | **OpenAI** | GPT-5.6 Sol, GPT-5.6 Terra, GPT-5.6 Luna, GPT-5.4 Mini | [platform.openai.com/api-keys](https://platform.openai.com/api-keys) | | **Claude (Anthropic)** | Claude Sonnet 5, Claude Haiku 4.5, Claude Opus 5, Claude Fable 5.1 | [console.anthropic.com](https://console.anthropic.com) | | **Gemini (Google)** | Gemini 3.8 Flash, Gemini 3.5 Flash-Lite, Gemini 3.1 Pro (Preview) | [aistudio.google.com/apikey](https://aistudio.google.com/apikey) | | **Grok (xAI)** | Grok 4.3 | [console.x.ai](https://console.x.ai) | | **Mistral AI** | Mistral Large, Mistral Small | [console.mistral.ai](https://console.mistral.ai) | | **DeepSeek** | DeepSeek V4 Pro, DeepSeek V4 Flash | [platform.deepseek.com](https://platform.deepseek.com) | | **[OpenRouter](#openrouter)** | 200+ models from all major providers, one key | [openrouter.ai/keys](https://openrouter.ai/keys) | | **Ollama (Local)** | Runs models on your own machine | No key needed | | **Custom (OpenAI-compatible)** | Any OpenAI-compatible API | From whoever runs the endpoint | ### Getting your first key 1. Pick a provider from the table above and follow its link. 2. Create an account and generate an API key. Most providers require billing details before a key will return anything; the free tiers that do exist are usually rate-limited rather than free-forever. 3. Copy the key **immediately** – most providers show it only once. 4. Paste it into the **API key** field below, then use **Test Connection** to confirm it works before you rely on it mid-job. Keys are stored locally in your Supervertaler data folder and are only ever sent to the provider’s own API endpoint. See [Privacy](/trados/privacy/) for what does and does not leave your machine. Caution An API key is a billing credential. Anyone who has it can spend money on your account. Do not paste one into a shared prompt, a support ticket, or a screenshot – and if you think one has leaked, revoke it from the provider’s console rather than just replacing it here. ## API key Enter the provider’s API key here. **Test Connection** checks it with a small call. ### One key file for every product (from v18.20.187) Keys are kept in one file shared by Supervertaler for Trados, Supervertaler for memoQ and Supervertaler Sidekick: `settings\api-keys.json` in your Supervertaler data folder, one line per provider, in plain text. Whatever you type here is written to that file, and the other products read it, so a key pasted once works everywhere. The file is filled from the plugin’s existing keys the first time it is missing, so nothing needs retyping after the update. You can also edit it in Notepad. The key box says so when a key plainly belongs to another service. Each provider’s keys have a recognisable start: Anthropic `sk-ant-`, OpenAI `sk-` or `sk-proj-`, Gemini `AIza`, xAI `xai-`, OpenRouter `sk-or-`. ## Model selection A dropdown showing a curated list of recommended models for the selected provider. ### The short list, and all models (from v18.20.187) By default the dropdown is a short list: the few models worth recommending for translation work, each with a one-line verdict. It is kept current with every release, and a model that has been superseded is removed from it rather than left in with a warning. Tick **Show all models** beside the dropdown to see everything the provider offers as well. Click **Fetch list** to ask the provider for its current list, using the API key in the box (it need not be saved yet) – Anthropic, OpenAI, Gemini, Mistral, DeepSeek, xAI, OpenRouter, Ollama and custom OpenAI-compatible endpoints all publish one. Fetching switches **Show all models** on. Models not in the short list appear with the provider’s own name for them; dated snapshots and models that are not for translating text (speech, image, transcription, embeddings) are left out. The fetched list and the tick box are remembered across restarts, and the Batch Operations and chat model menus follow them. This is the way to use a model released after your plugin build: click **Fetch list**, pick it, OK. ### Model ID Below the dropdown is an optional **Model ID** field. To use a model that isn’t in the curated list – a brand-new release, a preview model, or an OpenRouter router such as `openrouter/free` – type its exact model ID here. When filled, it overrides the dropdown selection; leave it blank to use the model picked from the dropdown. The field is available for every cloud provider. If you reopen Settings and a saved model isn’t in the curated list, it is shown back in the Model ID field. ## Ollama endpoint When using Ollama as the provider, this field sets the local endpoint URL. Defaults to: ```plaintext http://localhost:11434 ``` Change this only if you are running Ollama on a different port or a remote machine. ## DeepSeek [DeepSeek](https://platform.deepseek.com) is a Chinese AI lab offering high-quality models with competitive pricing. To use DeepSeek directly: 1. Create an account at [platform.deepseek.com](https://platform.deepseek.com) 2. Go to **API Keys** and create a key 3. In Supervertaler, select **DeepSeek** as the provider and paste your key DeepSeek models are also available via [OpenRouter](#openrouter) if you prefer a single-key setup. ## Custom OpenAI-compatible provider For providers that expose an OpenAI-compatible API (e.g., Azure OpenAI, together.ai, internal LLM gateways, local inference servers), configure these fields: | Field | Description | | ------------ | ------------------------------------------------------------- | | **Endpoint** | The base URL for the API (e.g., `https://your-server.com/v1`) | | **Model** | The model identifier to use (e.g., `llama-3-70b`) | | **API Key** | The authentication key for this endpoint | ### Managing multiple endpoints You can configure more than one custom endpoint and switch between them without re-entering credentials. Each endpoint is stored as a named **profile** in the **Profile** dropdown. | Button | Action | | ------ | ----------------------------------------------------------------------- | | **+** | Add a new endpoint (starts as “New Endpoint 1”, “New Endpoint 2”, etc.) | | **−** | Remove the currently selected endpoint | | **✎** | Rename the currently selected endpoint | Names are free-form labels – use whatever makes sense for your workflow (e.g. `Azure Production`, `Internal gateway – Mistral Large`, `Local Ollama`). Names must be unique within the list. Renaming is a UI-only change: the endpoint URL, model, and API key all stay attached to the same profile. ## OpenRouter [OpenRouter](https://openrouter.ai) is an API gateway that gives you access to 200+ models from OpenAI, Anthropic, Google, Mistral, Meta, and many others – all through a single API key. Instead of managing separate keys for each provider, you sign up once at OpenRouter and use one key for everything. ### Getting started 1. Create a free account at [openrouter.ai](https://openrouter.ai) 2. Go to **Keys** and create an API key 3. In Supervertaler, select **OpenRouter** as the provider and paste your key ### Curated model list The model dropdown includes a curated selection of the best models for translation: | Model | Description | | ------------------------ | ------------------------------------------------------------ | | **Claude Sonnet 4.6** | Recommended – best balance of speed, quality, and cost | | **Claude Opus 4.8** | Highest quality – Anthropic’s most capable model, 1M context | | **GPT-5.5** | Premium quality – OpenAI’s most advanced model | | **GPT-5.4 Mini** | Fast, affordable, and high quality for everyday translation | | **Gemini 3.1 Pro** | Google’s most advanced model, large context | | **Gemini 3 Flash** | Fast and affordable – great for large batch jobs | | **Gemma 4 31B** | Open-source – strong multilingual quality, 256K context | | **Gemma 4 26B MoE** | Open-source – near-31B quality at a fraction of the cost | | **Mistral Small 4** | Very fast and cheap – good multilingual support | | **Qwen 3.6 Plus (Free)** | Free – no API costs, good general-purpose quality | | **DeepSeek V4 Pro** | DeepSeek flagship – strong multilingual, competitive pricing | | **DeepSeek V4 Flash** | DeepSeek fast – great for high-volume translation | ### Using any OpenRouter model OpenRouter exposes far more models than the curated list above. To use one that isn’t listed, type its exact model ID into the **Model ID** field (see [Model selection](#model-selection)) – for example, `meta-llama/llama-3.1-70b-instruct`, `deepseek/deepseek-r1`, or a router such as `openrouter/free`. Browse all available models at [openrouter.ai/models](https://openrouter.ai/models). ### Pricing OpenRouter adds a **5.5% platform fee** on top of the underlying provider’s token price. For example, if Claude Sonnet 4.6 costs $3/$15 per million tokens at Anthropic, it costs approximately $3.17/$15.83 through OpenRouter. For a typical 5,000-word translation costing $0.50, the OpenRouter fee adds less than 3 cents. ## Context layer options These options control what additional context is included in AI prompts. The settings are split into two groups depending on which features they apply to. ### Which settings apply where | Setting | Chat & QuickLauncher | Batch Operations | | ------------------------------------ | :------------------: | :--------------: | | Termbases in AI prompts | Yes | Yes | | Include full document content | Yes | Yes | | Max segments | Yes | Yes | | Include term definitions and domains | Yes | Yes | | Log prompts to Reports | Yes | Yes | | Include TM matches | Yes | AutoPrompt only | | Surrounding segments | Yes | No | ### Context layers (Batch operations, Chat and QuickLauncher) These settings apply to **all** AI features – Chat, QuickLauncher, Batch Translate, and Batch Proofread. #### Include full document content When enabled, all source segments in the current document are sent to the AI so it can determine the document type (legal, medical, technical, marketing, etc.) and provide context-appropriate assistance. This uses more tokens but greatly improves response quality – the AI can tailor its terminology and style to the specific type of document you are translating. For very large documents, the content is automatically truncated to the configured maximum. The truncation preserves the beginning and end of the document (first 80% + last 20%). For Batch Operations, the document content is included once in the system prompt (shared across all batches), so the AI knows what kind of document it is translating even when processing individual batches of segments. #### Max segments The maximum number of source segments to include in the AI prompt when document content is enabled. Default: **500**. Range: 100–2000. Increase this for very large documents where you want the AI to see more content. Decrease it if you want to reduce token usage. #### List numbering as structure context (from v18.20.188; always on from v18.20.189) Word numbers claims, letters steps and bullets lists as paragraph properties, not as text. The segment grid never contains the `a)` or the `9.`, and until v18.20.188 neither did anything the AI received. On a patent, that means the model reads six unlettered steps and can conclude the source forgot to letter them – on a real document it translated “steps a. to f.” faithfully and then flagged it as a possible source defect, a note that would have reached the client. Batch Translate, Translate Segment, Clipboard Mode and SuperBench prefix the first segment of every numbered paragraph with the marker Word renders, inside a sentinel: `[#e)]het fixeren…`, `[#9.]Werkwijze…`, `[#•]een behuizing…`. A rule in the plugin’s own preamble tells the model that this is structure – use it to resolve cross-references and keep list items parallel, never translate it, never include it in the output. The rule ships with every request, including prompts you wrote yourself and AutoPrompt’s, because it lives in the plugin and not in a prompt template. **Preview prompt** shows exactly what goes out. The markers come from the original Word file that Studio keeps inside the sdlxliff, and are computed for the whole document at once, so a list that restarts at claim 11 reads `11.` and lettered steps that continue from one claim into the next keep counting – exactly as Word shows them. The batch log says how many markers were found and how many segments in the run carry one. Two safety nets: anything the model echoes back in a target is removed before the segment is written and logged in the batch log, and the TMX backup records the segment as Studio has it, without the sentinel. Files that are not Word documents, and Word files without any lists, get a one-line fallback rule instead: the numbering exists, is not in the text, and its absence is not a defect. v18.20.188 shipped this behind a checkbox so the first real runs could be checked; they showed no marker reaching a target, so from v18.20.189 it is simply on and the checkbox is gone. If you ever need it off – say, to compare prompts – add `"structureContext": false` to the `aiSettings` block of `settings.json` in `%LocalAppData%\Supervertaler.Trados\` while Studio is closed. #### Include term definitions and domains When enabled, term definitions, domains, and usage notes from your termbases are included alongside matched terminology in the AI prompt. This gives the AI deeper understanding of your terminology – for example, knowing that a term belongs to the legal domain or has a specific definition helps the AI use it correctly in both chat responses and batch translations. #### Include termbases in AI prompt Select which termbases are included in AI prompts. Terminology matches from enabled termbases are injected into the prompt to help the AI use the correct, approved terminology. For [AutoPrompt](/trados/generate-prompt/), **TermScan** automatically filters the termbase to only terms that appear in the document’s source text, keeping the prompt focused and within token limits. Caution **Only enable termbases you trust.** The AI will follow your termbase entries even when they are wrong. If a termbase contains inaccurate, outdated, or low-quality translations, the AI will be forced to use them – producing worse results than if no termbase were enabled at all. Modern LLMs are remarkably good at choosing correct terminology on their own. When in doubt, disable termbases and add terms incrementally as you review the AI’s output. ### Context layers (mostly Chat and QuickLauncher) These settings apply primarily to the **Supervertaler** chat window and **QuickLauncher** prompts. The exception is **Include TM matches**, which also feeds AutoPrompt – see the per-setting notes below. #### Include TM matches The behaviour of this checkbox depends on which feature is asking for context: * **Chat and QuickLauncher (live TM lookups).** When enabled, the AI gets translation memory matches – fuzzy and exact – for the active segment. This gives the AI reference translations from your project TMs to improve consistency. * **AutoPrompt (Batch Operations).** When enabled, [AutoPrompt](/trados/generate-prompt/) samples up to 50 already-translated, human-confirmed segment pairs evenly from the active document and includes them in the meta-prompt as in-project reference translations. This includes 100% / exact matches that have been applied and confirmed, fuzzy-and-edited segments, and segments translated from scratch – any segment with a Translated, Approved, or Signed-off confirmation level qualifies. AutoPrompt does **not** do live TM lookups; it samples confirmed segments straight from the document. * **Other Batch Operations (Translate, Proofread).** Unaffected by this checkbox – they always work segment-by-segment without TM reference pairs, regardless of how it’s set. #### Surrounding segments The number of segments before and after the active segment to include as context. Default: **5** (five segments on each side). Range: 1–20. This provides the AI with local context around the segment you are working on. It is also used for the `{{SURROUNDING_SEGMENTS}}` variable in [QuickLauncher prompts](/trados/settings/prompts/prompt-variables/). ### SuperMemory context These two toggles control whether [SuperMemory](/trados/ai-assistant/super-memory/) content is included in the AI context. #### Include memory bank in AI context When enabled, the AI reads the active bank’s `brief.md`, `terminology.md` and `style.md` - plus the `_shared` bank of house defaults - before every translation and chat message. This gives it the *reasoning* behind your decisions, not just the terms themselves. Caution **Off by default.** SuperMemory is a power-user feature that most translators should opt into deliberately. The simpler workflow – TermLens termbases + the AI context options above – covers the majority of needs. Enable this toggle once you have a populated memory bank and want the AI to consult it. #### Use memory bank when generating prompts (AutoPrompt) When enabled, SuperMemory content is included in the [AutoPrompt](/trados/generate-prompt/) meta-prompt so that generated translation prompts reflect your established client conventions, terminology reasoning, and style guides. Only effective when “Include memory bank in AI context” is also enabled. ## Prompt logging ### Log prompts and responses to Reports tab When enabled, AI operations are logged to the **Reports** tab in the Supervertaler Assistant panel. Each log entry shows: * The **feature and prompt name** (e.g. “QuickLauncher · Explain in Context”) * The **model used**, estimated **token counts**, **cost**, and **duration** * Expandable sections for the **system prompt**, **messages**, and **response** Click “Show system prompt…”, “Show messages…”, or “Show response…” to expand a section. Press **Escape** to collapse it. Use **Copy** to copy a single section, or **Copy all** to copy the full prompt details to your clipboard. This is useful for: * **Monitoring costs** – see exactly how many tokens each operation uses * **Debugging prompts** – inspect the full text sent to the AI to understand its behaviour * **Comparing models** – run the same prompt with different models and compare token usage ## Batch settings Configure the **batch size** for the [Batch Translate](/trados/batch-translate/) feature. This determines how many segments are sent to the AI provider in a single request. * A larger batch size is faster but uses more tokens per request * A smaller batch size is more granular and easier to review *** ## See Also * [Prompts](/trados/settings/prompts/) * [AI Cost Guide](/trados/ai-cost-guide/) * [TermLens Settings](/trados/settings/termlens/) * [Token Usage & Costs](/trados/usage-costs/) # Backup Use the **Export Settings** and **Import Settings** buttons in the **Backup** tab of the Settings dialogue to back up and restore your Supervertaler configuration. ## Export Click **Export Settings…** to save a copy of your current settings to a JSON file. Choose a location and filename – the default is `supervertaler-settings.json`. This file contains all your plugin settings: termbase paths, toggle states, font size, shortcut preferences, AI provider keys, model selections, and prompt configuration. ## Import Click **Import Settings…** to restore settings from a previously exported JSON file. The import process: 1. Validates that the selected file is a valid Supervertaler settings file 2. Creates an automatic backup of your current settings (`settings.backup.json`) 3. Replaces your current settings with the imported ones 4. Closes the Settings dialogue and applies the new settings immediately Caution Importing settings replaces **all** current settings. Your previous settings are automatically backed up in case you need to revert. ## Settings file location Your settings are stored at: ```plaintext %LocalAppData%\Supervertaler.Trados\settings.json ``` You can also manually back up or edit this file. After an import, the previous settings are saved as `settings.backup.json` in the same folder. # Project Settings Supervertaler for Trados automatically saves and restores your termbase configuration when you switch between Trados projects. This means each project can use its own Supervertaler database, write targets, and termbase settings without manual reconfiguration. ## How it works When you open a different Trados project (or switch to a document from another project), the plugin: 1. **Saves** the current project’s settings to a project-specific file 2. **Loads** the new project’s settings (if they exist) 3. **Reloads** the termbase with the new configuration If no project-specific settings exist yet (first time opening a project), the current global settings are used. Once you make any changes and click OK in Settings, those settings are saved for that project. ## What’s saved per project | Setting | Saved per project? | Notes | | ---------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------ | | Supervertaler database path | Yes | Each project can use a different `.db` file | | Enabled/disabled termbases (Read toggle) | Yes | Different termbases active per project | | Write targets | Yes | Different write targets per project | | Project termbase (pink highlighting) | Yes | Different project termbase per project | | MultiTerm visibility | Yes | Different MultiTerm termbases enabled per project | | AI context termbase filters | Yes | Different termbases in AI prompts per project | | Active prompt | Yes | Each project remembers its [active prompt](/trados/ai-assistant/super-memory/active-prompt/) for Quick Add and Batch Translate | | API keys and provider settings | No | Shared across all projects | | Panel font size | No | UI preference, shared | | Term shortcut style | No | UI preference, shared | | Dialogue sizes | No | UI layout, shared | ## Storage location Per-project settings are stored as individual JSON files inside your [user data folder](/trados/data-folder/): ```plaintext C:\Users\{you}\Supervertaler\trados\projects\ ``` Each file is named with a hash and the project name (e.g., `a1b2c3d4 - MyProject.json`). The JSON file also contains the original project path for reference. Caution **Moving a Trados project** to a different folder creates a new project key. The plugin will treat it as a new project and use global defaults until you reconfigure. The old project settings file remains in the `projects` folder and can be safely deleted. ## Interaction with global settings Global settings (`settings.json`) serve as the defaults for projects that don’t have their own settings file yet. When you open a project for the first time, the global termbase configuration is used. Once you change settings and click OK, those settings are saved for that specific project. Settings that are always global (API keys, font size, shortcut preferences) are never overridden by project settings. *** ## See Also * [TermLens Settings](/trados/settings/termlens/) * [AI Settings](/trados/settings/ai-settings/) * [Backup & Restore](/trados/settings/backup/) # Prompts Prompts tell the AI how to behave. The Prompt Manager lets you browse built-in domain prompts, create your own, and mark prompts as QuickLauncher shortcuts. #### Accessing the Prompt Manager Open the plugin **Settings** dialogueue and switch to the **Prompts** tab. ![]() #### Active prompt Right-click any translation prompt in the tree and choose **Set as active prompt for this project** to designate it as the active prompt. The active prompt is shown with a pin icon and bold blue text. It is used by [memory bank Quick Add](/trados/ai-assistant/super-memory/quick-add/) when appending terminology, and is auto-selected in the [Batch Translate](/trados/batch-translate/) dropdown. The active prompt is saved [per project](/trados/settings/project-settings/). #### What’s in this section * [**Built-in Prompts**](/trados/settings/prompts/built-in-prompts/) – the prompts that ship with the plugin, organised by category * [**Prompt Variables**](/trados/settings/prompts/prompt-variables/) – placeholders you can use to make prompts context-aware (language, segment, project) * [**Writing Custom Prompts**](/trados/settings/prompts/writing-custom-prompts/) – anatomy of a good prompt, worked examples, and tips * [**QuickLauncher Shortcuts**](/trados/settings/prompts/quicklauncher-shortcuts/) – marking prompts as QuickLauncher items, keyboard shortcuts (Ctrl+Alt+1-0), and reordering * [**Organising Prompts**](/trados/settings/prompts/organising-prompts/) – folders, drag-and-drop, and the prompt library structure * [**Prompt File Format**](/trados/settings/prompts/prompt-file-format/) – the `.svprompt` format, YAML fields, and creating/editing/deleting prompts #### See Also * [AutoPrompt](/trados/generate-prompt/) * [QuickLauncher](/trados/quicklauncher/) * [AI Settings](/trados/settings/ai-settings/) * [Batch Translate](/trados/batch-translate/) * [AI Proofreader](/trados/ai-proofreader/) * [SuperMemory](/trados/ai-assistant/super-memory/) * [Keyboard Shortcuts](/trados/keyboard-shortcuts/) # Built In Prompts The plugin ships with default prompts organised into three categories: | Category | Prompts | Used in | | ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------- | | **Translate** | Default Translation Prompt | Batch Translate mode | | **Proofread** | Default Proofreading Prompt | Batch Proofread mode | | **QuickLauncher** | Assess translation, Define, Explain (in general), Explain (within project context), Translate segment using fuzzy matches, Translate selection in context of current project | QuickLauncher menu | ### About the Default Proofreading Prompt The Default Proofreading Prompt is intentionally short. Most of the structure proofreading needs – persona, the five quality categories (accuracy / completeness / terminology / grammar / number formatting), the output format, the “no full corrected translations” rule, language-specific checks for Dutch / German / French – is **already in the hardcoded base** that every Batch Proofread uses, so the prompt itself only adds what the base doesn’t have: * **Default to OK** – raise an issue only when there’s a specific, demonstrable problem in the translation, never speculative concerns. * **Citation discipline** – terminology consistency claims must cite specific source segment numbers in the **Evidence:** field, against the full bilingual document context that’s auto-included. * **Source query distinction** – source-side errors (typos, duplications, internal inconsistencies) get prefixed with “Source query:” rather than triggering target changes. * **Explicit boundaries** – the AI doesn’t re-engineer the source, propose alternative terminology without a citation, flag stylistic preferences, or flag empty target lines. These behaviours target the false-positive patterns most users encounter: the AI fabricating “term X used elsewhere” claims, second-guessing the source’s substantive claims, and treating stylistic preferences as errors. See [AI Proofreader](/trados/ai-proofreader/) for the full picture, including the Evidence field on issue cards. # Organising Prompts The Prompt Manager tree mirrors the folder structure inside your `prompt_library` directory. You can: * **Create folders** – click **New Folder** in the toolbar * **Move prompts** – drag and drop a prompt onto a folder to move it * **Clone prompts** – right-click any prompt and select **Clone** to create a copy with “(2)” appended to the name, in the same folder as the original * **Delete prompts** – right-click a prompt or folder and select **Delete** * **Browse prompts** – click any prompt to preview its content in the detail pane # Prompt File Format Prompts are stored as `.md` files (Markdown with YAML frontmatter). This is the same format used by Supervertaler Workbench, so prompts are automatically shared between both applications via the shared `prompt_library` folder. Legacy `.svprompt` files are still loaded for backward compatibility. ```yaml --- type: prompt description: Patent and IP translation with strict terminology rules category: Translate --- You are an expert {{SOURCE_LANGUAGE}} to {{TARGET_LANGUAGE}} patent translator... ``` The example file above would be saved as e.g. `My Patent Prompt.md` and would appear in the prompt tree as **My Patent Prompt**. ### Naming: filename is authoritative The **on-disk filename** (without the `.md` extension) is the display name shown in the prompt selector. Renaming `My Patent Prompt.md` to `Client X – Patent EN.md` in Windows Explorer is all you need to do to change how the prompt appears in the tree – click **Refresh** in the Prompts tab to pick up the change. | YAML field | Description | | --------------------- | -------------------------------------------------------------------------------------------------- | | `type` | Document type – always `prompt` for prompt files | | `description` | Optional summary shown under the prompt name in the detail pane | | `category` | `Translate`, `Proofread`, or `QuickLauncher` – controls where the prompt appears | | `quicklauncher_label` | Short label for the QuickLauncher menu (optional, falls back to the filename) | | `default` | `true` for shipped prompts (managed by the plugin) | | `sort_order` | Numeric order within folder (lower values first). Set automatically by the ▲/▼ buttons. | | `name` | Ignored on read (legacy field, kept for backward compatibility). The filename is the display name. | ### System prompt The plugin automatically prepends a system prompt to every AI call. This system prompt includes language pair information, termbase terms (based on your [AI Context settings](/trados/settings/ai-settings/)), and TM matches when enabled. The content you write in a prompt `.md` file is the **user prompt** – it is sent after the system prompt. ### Creating and editing prompts #### New prompt 1. Optionally select a target folder (e.g. `Translate` or `Proofread`) in the tree before clicking **New** – the new prompt’s **Category** will be pre-filled from the selected folder. 2. Click **New** in the Prompts tab. 3. Fill in Name, Description, Category, and Content. 4. Click **Save**. #### Edit a prompt 1. Select a prompt in the list 2. Click **Edit** 3. Modify as needed and click **Save** #### Inserting variables While editing prompt content, press **Ctrl+,** to open the variable picker menu. This lists all available variables with a short description. Select a variable to insert it at the cursor position. If text is selected in the editor, it is replaced by the inserted variable. #### Delete a prompt 1. Select a custom prompt 2. Click **Delete** and confirm Built-in prompts cannot be deleted. Click **Restore** to recreate any built-in prompts you have removed. # Prompt Variables Variables are placeholders in your prompt text that are automatically filled in at runtime. Use them to make prompts context-aware without rewriting them for every project or language pair. ### Language variables – all contexts These work in Batch Translate, Batch Proofread, and QuickLauncher prompts: | Variable | Replaced with | Example | | --------------------- | -------------------------------------------------- | ------------------------- | | `{{SOURCE_LANGUAGE}}` | Full name of the source language, including locale | `Dutch (Belgium)` | | `{{TARGET_LANGUAGE}}` | Full name of the target language, including locale | `English (United States)` | ### Segment variables – QuickLauncher only These are only available in QuickLauncher prompts, because they refer to the specific segment active at the moment you trigger the menu: | Variable | Replaced with | Example | | -------------------- | ---------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | | `{{SOURCE_SEGMENT}}` | Full source text of the **active segment** | `De uitvinding heeft betrekking op een nieuwe werkwijze...` | | `{{TARGET_SEGMENT}}` | Full target text of the **active segment** (your translation so far – may be empty or partial) | `The invention relates to a novel method...` | | `{{SELECTION}}` | Text currently **selected** in the editor (source side preferred; falls back to target side) | `werkwijze` | ### Project variables – QuickLauncher only | Variable | Replaced with | | -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `{{PROJECT_NAME}}` | Trados project name (e.g. `Patent_NL_EN_2026`) | | `{{DOCUMENT_NAME}}` | Active file name (e.g. `source_document.docx`) | | `{{SURROUNDING_SEGMENTS}}` | N source segments before and after the active segment, with actual Trados segment numbers and the active segment marked `← ACTIVE`. N is set in **Settings → AI Settings → Surrounding segments** (default: 5). | | `{{PROJECT}}` | All source segments in the document, numbered with their actual Trados segment numbers. In multi-file projects a `=== File N ===` header separates each file (Trados restarts segment numbering per file). | | `{{TM_MATCHES}}` | Translation memory fuzzy matches (≥70%) for the active segment, showing match percentage, TM name, source text, and target text. If no matches meet the threshold, replaced with “(no fuzzy matches above 70%)”. | Caution `{{PROJECT}}` sends the entire document to the AI and uses significantly more tokens than other variables. For a 10,000-word document, this costs roughly 4–5 cents per call with a Sonnet-class model. Reserve it for prompts where full document context genuinely matters. To keep the chat history readable, the chat bubble shows a compact summary (e.g. `[source document – 47 segments]`) instead of the full source text. The complete document is still sent to the AI. ### Scope: which prompts see which variables The variables above are **only substituted in QuickLauncher prompts**. In Batch Translate and Batch Proofread custom prompts, only the two **language variables** (`{{SOURCE_LANGUAGE}}` and `{{TARGET_LANGUAGE}}`) get filled in – any other variable left in the prompt body will be replaced with an empty string. This isn’t a limitation in practice. The batch flows assemble a richer system prompt automatically, with no variables required: * **Batch Translate** automatically includes source-only document context (when **Include document context** is on in [AI Settings](/trados/settings/ai-settings/)), termbase entries, and language-specific checks. * **Batch Proofread** automatically includes the **full bilingual document context** (source + target, untruncated), termbase entries, and language-specific checks. So the right place for your custom prompt content in batch mode is to **complement** what’s already there – domain-specific guidance, citation discipline, project-specific terminology preferences – rather than try to re-inject document context with `{{PROJECT}}`. If you want to see exactly what gets sent to the AI for a batch run – fully assembled, including the auto-injected context – click the **👁 Preview prompt** link next to the Translate / Proofread button on the Batch Operations tab. See [Batch Operations](/trados/batch-operations/) for details. # Quicklauncher Shortcuts ### Marking a prompt as a QuickLauncher shortcut To make a custom prompt appear in the QuickLauncher right-click menu (`Alt+Q`), set `category: QuickLauncher` in the YAML frontmatter: ```yaml --- name: Explain selected term description: Explains the selected term in translation context category: QuickLauncher quicklauncher_label: Explain term --- Your prompt content here... ``` | Field | Description | | ------------------------- | ------------------------------------------------------------------------ | | `category: QuickLauncher` | Marks this prompt as a QuickLauncher item | | `quicklauncher_label` | Optional short label shown in the menu – falls back to `name` if omitted | You can also organise QuickLauncher prompts by placing them in a folder called `QuickLauncher` inside your `prompt_library` folder. Any prompt in that folder is automatically treated as a QuickLauncher prompt. ### Keyboard shortcuts for QuickLauncher prompts You can assign keyboard shortcuts (Ctrl+Alt+1 through Ctrl+Alt+0) to individual QuickLauncher prompts for instant access without opening the Alt+Q menu. 1. Open **Settings → Prompts** 2. Select a QuickLauncher prompt in the tree 3. In the detail pane on the right, use the **Shortcut** dropdown to assign a slot 4. Click **OK** to save Each shortcut can only be assigned to one prompt. If you assign a shortcut that is already in use, it is automatically cleared from the other prompt. Assigned shortcuts are shown next to prompt names in the Alt+Q menu and in the Trados keyboard shortcuts settings (File → Options → Keyboard Shortcuts → Supervertaler for Trados). ### Reordering prompts Use the **▲** and **▼** buttons in the toolbar to change the order of prompts within a folder. This is especially useful for QuickLauncher prompts, as the order in the tree determines the order in the Alt+Q menu. The order is saved in each prompt’s YAML frontmatter as a `sort_order` field. # Writing Custom Prompts ### Anatomy of a prompt A good prompt has three parts: 1. **Role** – tells the AI who it is 2. **Task** – tells the AI what to do 3. **Constraints** – tells the AI what to avoid or preserve Here is an annotated example for a Batch Translate prompt: ```plaintext You are an expert {{SOURCE_LANGUAGE}} to {{TARGET_LANGUAGE}} patent translator. ← Role + language variables Translate the source segment provided. Return only the translated text – ← Task no commentary, no explanations, no repetition of the source. Preserve all tag placeholders exactly as they appear (e.g. , ). ← Constraints Preserve numbers, units, and chemical formulas without conversion. Use formal, technical register throughout. ``` ### Example QuickLauncher prompt – explain a selected term This prompt uses `{{SELECTION}}` to ask the AI to explain a selected term in context: ```plaintext The user is translating a patent from {{SOURCE_LANGUAGE}} to {{TARGET_LANGUAGE}}. The selected term is: {{SELECTION}} Please explain what this term means in the context of patent translation, suggest the standard {{TARGET_LANGUAGE}} equivalent, and note any regional or register variations the translator should be aware of. ``` When the translator selects “werkwijze” in the source segment and triggers this prompt via QuickLauncher, the AI receives: ```plaintext The user is translating a patent from Dutch (Belgium) to English (United States). The selected term is: werkwijze Please explain what this term means... ``` ### Example QuickLauncher prompt – assess the current translation This prompt uses `{{SOURCE_SEGMENT}}` and `{{TARGET_SEGMENT}}` to ask the AI to review the translation of the active segment: ```plaintext Source ({{SOURCE_LANGUAGE}}): {{SOURCE_SEGMENT}} My translation ({{TARGET_LANGUAGE}}): {{TARGET_SEGMENT}} Assess how I translated the current segment. Point out any inaccuracies, awkward phrasing, or terminology issues, and suggest improvements. ``` ### Example QuickLauncher prompt – translate a selected term in context ```plaintext Source segment ({{SOURCE_LANGUAGE}}): {{SOURCE_SEGMENT}} Current translation ({{TARGET_LANGUAGE}}): {{TARGET_SEGMENT}} The translator has selected this word or phrase: {{SELECTION}} Suggest the best {{TARGET_LANGUAGE}} translation for "{{SELECTION}}" given the full segment context above. Give a short explanation of your reasoning. ``` ### Example QuickLauncher prompt – translate a term using surrounding passage Uses `{{SURROUNDING_SEGMENTS}}` for a wider context window than just the active segment: ```plaintext I am translating a {{SOURCE_LANGUAGE}} patent into {{TARGET_LANGUAGE}}. The selected term is: {{SELECTION}} Here is the passage surrounding the active segment: {{SURROUNDING_SEGMENTS}} Suggest the best {{TARGET_LANGUAGE}} translation for "{{SELECTION}}" given the surrounding context. Briefly explain your reasoning. ``` ### Example QuickLauncher prompt – full-document term consistency check Uses `{{PROJECT}}` to give the AI the entire source document. Useful for checking whether a key term is used consistently, or for understanding a term’s meaning across all its occurrences. Reserve this for important queries – see the token cost note in [Prompt Variables](/trados/settings/prompts/prompt-variables/). ```plaintext I am translating a {{SOURCE_LANGUAGE}} patent ({{DOCUMENT_NAME}}) into {{TARGET_LANGUAGE}}. Project: {{PROJECT_NAME}} Here is the complete source text: {{PROJECT}} The selected term is: {{SELECTION}} What is the most accurate and consistent {{TARGET_LANGUAGE}} translation for "{{SELECTION}}" throughout this document? Note any variation in meaning between occurrences and recommend which translation to use where. ``` ### Example QuickLauncher prompt – check a segment against the full document After sending `{{PROJECT}}`, the AI knows the segment numbers shown in Trados, so you can ask about specific segments by number in follow-up messages – or ask in the prompt itself: ```plaintext I am translating a {{SOURCE_LANGUAGE}} patent into {{TARGET_LANGUAGE}}. Here is the source document: {{PROJECT}} I am currently working on segment {{SOURCE_SEGMENT}} (shown as [{{SOURCE_SEGMENT}}] above). My translation is: {{TARGET_SEGMENT}} Does this translation accurately reflect the source and maintain consistency with the terminology used elsewhere in the document? Point out any issues. ``` ### Tips for effective prompts * **Be explicit about output format.** If you only want the translation, say “Return only the translated text.” If you want an explanation, describe the expected structure. * **Use language variables.** Hardcoding “Dutch to English” breaks the prompt when you switch projects. Always use `{{SOURCE_LANGUAGE}}` and `{{TARGET_LANGUAGE}}`. * **Keep QuickLauncher prompts focused.** A narrow, specific task works better than a broad one – except when you deliberately need the full document context via `{{PROJECT}}`. * **Use `{{SURROUNDING_SEGMENTS}}` instead of `{{SOURCE_SEGMENT}}` when context matters.** The surrounding passage often gives the AI enough context for a better answer at a fraction of the cost of `{{PROJECT}}`. * **Use `{{PROJECT}}` sparingly.** It is best suited for high-stakes queries on short-to-medium documents – terminology consistency checks, key term decisions, or reviewing a handful of specific segments. Avoid it in prompts you run on every segment. * **Segment numbers in `{{PROJECT}}` match the Trados editor.** After sending `{{PROJECT}}`, you can ask the AI about “segment 4” or “segment 12” and it will know exactly which segment you mean – the same number shown in the Trados grid. * **Use `{{TM_MATCHES}}` to leverage existing translations.** When a segment has a high fuzzy match, the AI can use it as a starting point – especially useful for repetitive or formulaic content like patents and legal texts. * **Batch Translate prompts receive one segment at a time.** You do not need to handle lists of segments or loop logic. * **Proofread prompts receive multiple segment pairs.** The built-in proofreading prompt shows the expected input/output format – follow that structure if you write a custom one. # Termlens Configure how TermLens loads and displays terminology in Trados Studio. ## Accessing TermLens settings Click the **gear icon** in the TermLens panel, or open the plugin **Settings** dialogue and switch to the **TermLens** tab. ## Database path The path to your Supervertaler termbase `.db` file. Click **Browse** to select a database, or **Create New** to start with an empty one. ## Termbase toggles Each Supervertaler termbase in the database has three toggles. See [Termbase Management](/trados/termbase-management/) for full details. | Toggle | Purpose | | ----------- | ------------------------------------------------------------------------------------- | | **Read** | Load terms for matching –only termbases with Read enabled appear in TermLens | | **Write** | Receive new terms added via the [quick-add shortcuts](/trados/termlens/adding-terms/) | | **Project** | Mark as the project termbase (shown in pink, prioritised) | ### Confirm dialog for non-matching termbases When you tick **Write** or **Project** on a termbase whose declared language pair does not match the active project (for example, ticking an EN→NL termbase as Write while you have a DE→FR project open), a confirmation dialog appears: > *“\” is a EN → NL termbase, but the active project’s source language is German. Setting it as a Write termbase means new terms added during this project will be written into a termbase whose language pair doesn’t match.* > > *This is occasionally intentional (multilingual or global termbases, bootstrapping a new direction) – tick “Yes” to continue. The plugin will remember this choice for this termbase and won’t ask again until you untick the box.* Click **Yes** to keep the tick, or **No** to revert it. The plugin remembers each “Yes” answer per termbase, so once you have explicitly confirmed a non-matching termbase you are not asked again on subsequent ticks. **Unticking the box clears that confirmation** – a future re-tick will re-ask. This is intentional: an untick is taken as a clear signal that you are reconsidering, so the next tick deserves a fresh look. The header **tick-all** on the Write column also respects this guard – non-matching termbases that haven’t been individually confirmed are skipped during a bulk tick, so a quick “tick everything” can’t accidentally enable unrelated termbases for write. The **Read** column is intentionally exempt from the dialog – there is no harm in *reading* a non-matching termbase (its terms simply won’t match anything in your segments), only in writing into it. ## MultiTerm termbases If your Trados project has MultiTerm termbases (`.sdltb` files) attached, they appear at the bottom of the termbase list with a **\[MultiTerm]** label and a light green row background. The **Read** toggle controls visibility in TermLens; **Write** and **Project** are always disabled because MultiTerm termbases are read-only. To add or remove MultiTerm termbases, use Trados Studio’s **Project Settings > Language Pairs > Termbases**. See [MultiTerm Support](/trados/multiterm-support/) for full details. ## Auto-load on startup When enabled, the plugin automatically loads the termbase database when Trados Studio opens. This means terms are available immediately when you start translating, without needing to open the settings first. If disabled, the termbase loads the first time you open the TermLens settings or click the TermLens panel. ## Case-sensitive matching By default, TermLens matches terms regardless of letter case – “polymer”, “Polymer”, and “POLYMER” all match the same term entry. Enable **“Enable case-sensitive matching globally”** to require exact case matching across all termbases. You can also control case sensitivity per termbase using the **CS** checkbox in the termbase grid. When the CS checkbox is ticked for a termbase, that termbase always matches case-sensitively; when unticked, it matches case-insensitively. ## Adapt term capitalisation **Adapt term capitalisation to the segment** (on by default) makes TermLens display and insert target terms with the capitalisation of the source occurrence in the segment rather than the capitalisation stored in the termbase: * A term stored as “More preferably” shows and inserts as **“more preferably”** when the segment contains it lower-case mid-sentence * A term stored lower-case is **capitalised** when the occurrence starts the sentence * An **ALL-CAPS** occurrence (e.g. in a heading) upper-cases the whole inserted term The adaptation applies everywhere a term is displayed or inserted: the TermLens chips, Alt+digit shortcuts, the TermLens popup and TermPicker. ## Panel font size Adjust the font size used in the TermLens display panel. Valid range: **7 pt** to **16 pt**. Increase the font size if TermLens text is hard to read; decrease it to fit more terms on screen. ## Term shortcuts Choose how Alt+digit shortcuts work when a segment has more than 9 matched terms: * **Sequential** (default) – type the term number digit by digit. Alt+45 inserts term 45. Badges show clean sequential numbers (10, 11, 12, …). There is a brief delay after each digit while the system waits for a possible next digit. * **Repeated digit** – press the same digit key multiple times. Alt+55 inserts term 14 (the 5th term in the second tier). Badges show repeated digits (11, 22, 333, …). No delay, but the badges are less intuitive. Both modes behave identically when a segment has 9 or fewer matches – pressing Alt+N inserts immediately with no delay. ## Shortcut delay Controls how long the system waits for the next digit in **Sequential** mode (in milliseconds). Default: **1100 ms**. Valid range: **300 ms** to **3000 ms**. Increase the delay if you need more time between keystrokes. Decrease it if you find the pause too long when inserting single-digit terms in segments with 10+ matches. This setting has no effect in Repeated digit mode. See [Keyboard Shortcuts](/trados/keyboard-shortcuts/) for the full reference. *** ## See Also * [Termbase Management](/trados/termbase-management/) * [MultiTerm Support](/trados/multiterm-support/) * [AI Settings](/trados/settings/ai-settings/) * [TermLens overview](/trados/termlens/) # Usage Statistics Supervertaler for Trados sends one anonymous, lightweight ping to the developer at startup so he can see how many people are using the plugin and what environments they are running it on. The dialogue below appears once after install or update, and the feature can be switched off at any time.  #### How it works * **Default-on, opt-out** – on first launch after install or update, an informational dialogue (shown above) tells you exactly what is collected and gives you a one-click **Turn it off** button. You don’t have to do anything to keep it enabled – the dialogue’s default action (the bold **Keep it on** button, Enter, Esc, or the X-close) all keep it enabled. Your choice is remembered, and the dialogue isn’t shown again. * **Minimal data** – a single lightweight ping is sent once per session on plugin startup. The only data included is: * A random anonymous ID (a UUID generated locally on your machine – not tied to any account, machine, or identity) * Plugin version (e.g. 4.19.108) * OS version (e.g. Windows 11) * Trados Studio version * System locale (e.g. en-GB) * **Country detection** – the hosting provider (Cloudflare) determines your country from the network connection. No IP addresses are stored. * **Silent failure** – if the ping fails (no internet, firewall, etc.), nothing happens. No retries, no queuing, no error messages. * **First-party only** – data is sent to a Supervertaler-operated Cloudflare Worker endpoint. No third-party trackers, no Google Analytics, no advertising platforms. #### What is NOT collected * No translation content * No termbase data * No file names or project names * No personal information (name, email, etc.) * No information about which features you use or how often * No API keys or credentials #### Changing your preference You can change your choice at any time: 1. Open **Settings** (click the gear icon in the Supervertaler Assistant panel) 2. In the **TermLens** tab, scroll to the **Privacy** section 3. Check or uncheck **“Share anonymous usage statistics (no personal data)”** 4. Click **OK** The change takes effect on the next Trados Studio session. #### Why this exists As a solo developer, usage statistics provide invaluable insight into: * How many people are actually using the plugin * Which Trados Studio versions to prioritise for testing and compatibility * Which OS versions and locales are most common * Whether users run Trados on a Mac (via Parallels) or natively on Windows This information directly informs development priorities and compatibility testing. #### Transparency The full source code for both the plugin-side statistics and the server-side endpoint is publicly available: * **Plugin code**: [`Core/UsageStatistics.cs`](https://github.com/Supervertaler/Supervertaler-for-Trados/blob/main/src/Supervertaler.Trados/Core/UsageStatistics.cs) on GitHub * **Server code**: The Cloudflare Worker that receives the pings is also open source You can verify exactly what data is sent by inspecting the code yourself. # Trados Studio 2026 & .ttb Termbases Trados Studio 2026 introduces a new termbase format –the SQLite-based **`.ttb`** file –and drops the legacy MultiTerm engine that earlier versions relied on. Supervertaler for Trados supports Studio 2026 through a dedicated build that reads `.ttb` termbases directly. ## Two builds, one product Supervertaler for Trados ships as two separate plugin builds from the same codebase: | Build | For | Termbase format | | ------------------------------------------ | ------------------ | ------------------ | | **Supervertaler for Trados** | Trados Studio 2024 | MultiTerm `.sdltb` | | **Supervertaler for Trados (Studio 2026)** | Trados Studio 2026 | `.ttb` | Install the build that matches your Studio version. The 2024 build will not load in Studio 2026, and vice versa, because the two Studio releases use different plugin frameworks and termbase engines. ## Version numbering Each build’s **major version tracks the Trados Studio major it targets**, so the two builds always carry distinct, non-colliding version numbers that share the same tail: | Build | Example version | | ------------------ | --------------- | | Trados Studio 2024 | `18.20.86` | | Trados Studio 2026 | `19.20.86` | So you can tell at a glance which Studio a build is for: a `18.x` plugin is for Studio 2024, a `19.x` plugin is for Studio 2026. (Releases up to and including `4.20.85` used a single shared number for both builds.) ## TermLens and `.ttb` termbases In Studio 2026, TermLens reads the new `.ttb` termbases attached to your project automatically –there is nothing to configure. Terms appear as **green chips** in the TermLens panel, exactly as MultiTerm terms do in the 2024 build, and behave the same way (click to insert, or **Alt+1**–**Alt+9** to insert by number). `.ttb` termbases are **read-only** in TermLens, just like MultiTerm termbases. To add or edit terms, use Studio 2026’s built-in Termbases view. Everything else – Supervertaler, Batch Translate, SuperSearch, TermPicker, AI terminology injection – works identically across both builds. ## What about my existing `.sdltb` termbases? Studio 2026 cannot open `.sdltb` files directly; the MultiTerm engine that read them is no longer part of the base install. Instead, **RWS provides conversion to the new `.ttb` format**: * The **Termbases view** in Studio 2026 has a wizard to migrate `.sdltb` → `.ttb`. * Opening a project package that contains an `.sdltb` termbase converts it to `.ttb` on the fly. * When a 2026 user sends a package back to someone still on Studio 2024, Studio can create a “compatible” package that the older version converts back to `.sdltb` automatically. Once your termbase is in `.ttb` form, TermLens picks it up automatically. There is no separate step in Supervertaler –convert in Studio, and the terms appear. ## Technical notes * `.ttb` is a SQLite 3 database with full-text search. TermLens opens it in read-only mode, so Studio can keep using it at the same time with no risk of corruption. * Studio 2026 is a 64-bit application. The 2026 build is 64-bit to match; the 2024 build remains 32-bit/AnyCPU for the MultiTerm JET driver it depends on. ## See also * [MultiTerm Support](/trados/multiterm-support/) –the equivalent `.sdltb` workflow in Studio 2024 * [TermLens](/trados/termlens/) * [Installation (Trados)](/trados/installation/) * [Troubleshooting](/trados/troubleshooting/) # SuperBench > Translate the same text with three models under identical settings, and have a judge say which to use for this project. Which model should you use for this project? SuperBench answers that with evidence from the document in front of you rather than from a benchmark of somebody else’s text. Available from v18.20.187. ## What it does 1. You pick **three models**, one per slot – any provider each. The defaults are Claude Opus 5, GPT-5.6 Sol and Gemini 3.1 Pro. 2. You pick a **judge** – Claude Fable 5.1 by default – and how many segments of the open document to use. Twenty is a good start. 3. Each model translates those segments through the batch pipeline itself. The selected prompt, the termbase terms that occur in the text, the document context, SuperMemory and the batch size are exactly what a real Batch Translate would send; only the model changes. **Nothing is written to the document.** 4. The judge reads the source and the three translations **blind** – labelled A, B and C in a shuffled order, so no brand name colours the verdict – together with the same approved terms and instructions, and writes a short report: a ranked verdict, the significant errors per candidate with segment numbers, how each handled terminology and tags, and a recommendation for this project. 5. The translations appear side by side above the report, with each model’s cost and time. The whole thing is saved as Markdown in `trados\reports` inside your data folder, and **Save report…** writes a copy wherever you like.  A finished run on the inline-formatting test document: Claude Opus 5, GPT-5.6 Sol and Gemini 3.1 Pro side by side, judged by Claude Fable 5.1. The legend above the report maps the judge's letters to the models. ## Running it 1. Open the document and set up the Batch Operations tab as you would for a real run: the prompt, and the termbases ticked for AI on the Termbases tab. 2. Click **⚖ SuperBench…** next to **Preview prompt**. 3. Choose the three models, the judge and the number of segments. The line under the segment count shows the estimated cost of the three runs and the judge’s call. 4. Click **Run SuperBench**. The status line follows the runs; **Cancel** stops after the current call. ## Reading the report The legend at the top of the report maps the judge’s letters to the models. The judge’s own text uses only the letters. * **Verdict** – the best candidate for this text, and a ranked list. * **Errors** – the significant errors per candidate, each with the segment number and the words in question. “None found” means the judge looked and found nothing. * **Terminology** and **Tags** – whether the approved terms were used and the inline tags kept. * **Recommendation** – which to use for this project, and whether the difference is worth paying for. A judge is a model too. Treat the report as a well-informed second opinion: read the segments it names before deciding, and run it again on a different stretch of the document if the verdict is close. ## Cost Three batches of twenty segments plus one judge call costs a few cents with the default models; the estimate is shown before you run, and the actual cost per model is in the report. Every call is logged like any other AI call, so it appears in the Reports tab and the usage ledger. # SuperSearch SuperSearch is a cross-file search and replace tool that lets you find text across **all SDLXLIFF files** in your Trados project – not just the file you currently have open – and, optionally, across the project’s **translation memories** as well. It lives in its own dockable panel, so you can keep it visible while you translate. Matching text is highlighted in yellow in the results grid, making it easy to spot exactly where the search term appears in each segment. [SuperSearch in action – cross-file search across a Trados project](https://www.youtube.com/embed/549Ulc92FiU) ## Opening the Panel There are three ways to open SuperSearch: | Method | Description | | --------------- | -------------------------------------------------------------------------- | | **View menu** | Go to **View > SuperSearch** | | **Right-click** | Right-click in the editor and choose **SuperSearch** from the context menu | | **Keyboard** | Press **Alt+S** | The panel docks at the bottom of the editor by default, but you can drag it anywhere – left, right, floating, or even to a second monitor. Trados remembers the position between sessions. ![]() ## Searching Type your search query in the text box and press **Enter** (or click **Search**). ### Search Modes The **mode** dropdown in the search bar controls where SuperSearch looks: | Mode | Searches | | ----------------- | ------------------------------------------------------------------------------------------------------ | | **Everything** | Project files, translation memories *and* termbases, merged into one result list | | **Project files** | The project’s SDLXLIFF files | | **TMs** | Only the project’s translation memories – a concordance search, like Studio’s built-in Concordance | | **Termbases** | Only your terminology – Supervertaler, MultiTerm (`.sdltb`) and Trados `.ttb` termbases *(v18.20.155)* | The mode is remembered across sessions until you change it. Translation-memory results are found via the project’s attached file-based TMs (`.sdltm`) – read from the project settings and the project’s `Tm` folder. Server-based (GroupShare) TMs are not searched. TM hits obey the same **Aa**, **.\***, and **Word** options as file results, and the **Scope** dropdown maps to source-side / target-side concordance. The TM list is re-checked every time you search, so a TM you attach to the project mid-session is picked up without reopening the project. SuperSearch searches every attached TM regardless of its **Enabled** / **Concordance** state in the project’s TM settings – use the **TMs** button (see below) to narrow the list. ### Searching your termbases *(from v18.20.155)* *“Where does this phrase appear?”* and *“what have I called this term?”* are the same question at different granularities, so SuperSearch answers both. Terminology is searched alongside files and TMs in **Everything**, or on its own in **Termbases**. All three kinds of termbase are included, with nothing extra to configure: * **Supervertaler termbases** – every termbase in your shared database * **MultiTerm** – the `.sdltb` termbases attached to the Trados project * **Trados `.ttb`** – the Studio 2026 termbase format Terminology is matched **in your project’s direction**: a termbase declared the other way round (an EN→NL termbase in an NL→EN project) is oriented before matching, so the **Src** box always means *the language you translate from* – not “whichever column that particular termbase calls source”. This is the same treatment TermLens gives your terminology. Searches read the terminology TermLens already holds in memory, so a termbase search is effectively instant. (Immediately after opening a project TermLens may still be loading, in which case the first search falls back to reading the database and takes longer.) Only the termbases you have **switched on** are searched – Supervertaler termbases with their **Read** tick set, and MultiTerm/`.ttb` termbases enabled in Trados Project Settings. The Read column is your statement of which terminology applies to the job in hand, so SuperSearch honours it rather than searching everything you own. Termbase hits show the **termbase name in green** and its **kind** in the Status column (`Supervertaler`, `MultiTerm` or `TTB`). #### Editing a term from the results *(from v18.20.187)* Right-click a Supervertaler termbase hit and choose **Edit term…** to open it in the **Edit term entry** dialog – the same one TermLens opens from a chip – with the termbase already resolved. Save, and the results refresh to show the corrected term; TermLens picks the change up immediately. Right-clicking selects the row under the pointer, so you need not click it first. Two kinds of hit cannot be edited here, and the menu says so if you try: **MultiTerm** and `.ttb` entries, which are read-only throughout Supervertaler (edit them in MultiTerm), and hits from a termbase that SuperSearch read straight from the database because TermLens had not finished loading it – open that termbase in the Termbase Editor instead, or search again once TermLens has loaded. ### Searching the web *(from v18.20.181)* The one place a translator still had to leave Studio was the web. SuperSearch now covers that too: select a term, press **Alt+W**, and every reference site you have switched on opens with the query and your project’s language pair already filled in. There is nothing to type and no language dropdown to set. You can also right-click in the editor and choose **Search the web**, or use the **🌐** button in the SuperSearch bar. #### Choosing which sites to search Click **Web (n)** in the SuperSearch bar – it sits beside **Files**, **TMs** and **TBs**, and works the same way. Forty-one sites ship with the plugin, of which five are on out of the box: **Beijerterm**, **IATE**, **Linguee**, **ProZ.com** and **Reverso**. The other thirty-six cover bilingual dictionaries (Glosbe, WordReference, bab.la), EU and legal terminology (EUR-Lex, EuroTermBank, Juremy, GEMET), encyclopaedic sources (Wikipedia, Wiktionary, Wikidata), English monolingual and writing references (Collins, Merriam-Webster, Oxford Collocations, SkELL, Etymonline), Dutch resources (Woordenlijst, Synoniemen.net, de Financiële Begrippenlijst), medical databases (EMA, EMC) and general search (Google, Google Patents, GitHub Code). Only five are enabled initially on purpose – forty tabs opening on your first search would be a poor introduction. Tick whichever you actually use. **Adding your own** takes a name and a URL template: `{query}` for the search term, plus `{sl}` and `{tl}` for the language codes where the site needs them. #### Where the results open A checkbox in that same dialog decides. Neither option is a fallback for the other, and both are worth having: * **In a Supervertaler window** – one window with a tab per site, reused for every search so tabs refresh in place rather than leaving a trail of windows behind. Tabs load only when you click them. * **In your own browser** – one new window containing all the tabs, which you close when you are done. Your browser brings your ad blocker and your signed-in sessions with it. #### Terms taken from the target side A term selected in the **target** is looked up **in the target language**. Searching a Dutch word in an EN→NL project queries the sites as nl→en, not en→nl – the latter is how you get a screen of nothing and conclude the site is broken. #### Sites that ask you to prove you are human Some sites, ProZ.com in particular, block embedded browsers. When that happens the tab shows a banner offering to hand the page to your own browser, where you are usually signed in and pass instantly. It is an offer rather than an automatic jump, so nothing pulls you out of the editor mid-segment – and if the check clears by itself, the page is still there underneath. ### Search Options | Option | Description | | ------------------ | ------------------------------------------------------------------------------------------------- | | **Scope** dropdown | Choose *Source & Target* (default), *Source only*, or *Target only* | | **Aa** checkbox | Case-sensitive search – when unchecked, “Hello” matches “hello”, “HELLO”, etc. | | **.\*** checkbox | Treat the query as a regular expression (see [Regex tips](/trados/supersearch/#regex-tips) below) | | **Word** checkbox | Match whole words only – “cat” won’t match “category” or “scatter”. Ignored when **.\*** is on | SuperSearch displays all matching segments in the results grid. The status bar shows the number of results, what was searched (files and/or TMs), and how long the search took. ### Results Grid Each row shows one matching segment, one TM entry, or one termbase entry: | Column | Description | | ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Found in** | The project-file name, the translation-memory name (blue), or the termbase name (green). Hover for the full path | | **#** | Segment number within the file; for TM results, the concordance match score; empty for termbase entries | | **Source** | Source text – matching text is highlighted in yellow | | **Target** | Target text – matching text is highlighted in yellow | | **Status** | Confirmation status (Not Translated, Draft, Translated, etc.), “TM” for TM results, or the termbase kind (`Supervertaler`, `MultiTerm`, `TTB`) for terminology | ### Preview Pane Below the results grid is a preview pane showing the **full source and target text** of the selected result, side by side, with the match highlighted in yellow. This is handy when a segment is too long to read in its grid row. Click any result row to update the preview, and drag the splitter bar between the grid and the preview pane to resize it. The text in both preview boxes is **selectable**: drag to select, press **Ctrl+C** to copy, or right-click for a menu with **Copy**, **Select All**, **Copy source**, and **Copy target**. This makes it easy to reuse a previous translation verbatim – select the target phrase and paste it straight into your active segment. ## File, TM and Termbase Selection Four buttons in the search bar let you narrow what SuperSearch looks at – **Files** for the project’s SDLXLIFF files, **TMs** for the project’s translation memories, **TBs** for your termbases *(v18.20.155)*, and **Web** for reference sites *(v18.20.181)*. Each button shows how many items are included: * **Files (16)** – all 16 files in the project are included * **Files (12/16)** – 12 out of 16 files are included (4 excluded) * **TMs (3)** – all 3 project TMs are included * **TMs (1/3)** – 1 of 3 TMs is included (2 excluded) * **TBs (2)** – both available termbases are included * **Web (5/41)** – 5 of the 41 available web resources are switched on Files, TMs and termbases are all discovered when the project opens, so the counts are filled in before your first search. Web resources are your own standing choice rather than a property of the project, so that count is the same in every job until you change it. Click any button to open its selection dialog: 1. A list shows all the files (or TMs, or termbases) found, with checkboxes 2. **Check** the items you want to include in the search 3. **Uncheck** the items you want to exclude 4. Use **Select All** or **Select None** to quickly toggle everything 5. Click **OK** to apply The **Files** filter applies in **Project files** and **Everything** modes; the **TMs** filter applies in **TMs** and **Everything** modes; the **TBs** filter applies in **Termbases** and **Everything** modes. Termbases are listed as *name (kind)* – for example `BEIJER (Supervertaler)` – so two termbases that share a name remain distinguishable. ## Navigating to a Segment **Double-click** a row (or select it and press **Enter**) to jump to that segment in the editor. * If the segment is in the **currently active file**, Trados navigates to it directly. * If the segment is in a **different file**, SuperSearch attempts to switch to that file and navigate to the segment. If the file is not loaded in the editor, you may need to open it first. * **TM results** can’t be navigated to – they aren’t document segments. Double-clicking a TM row just reminds you to use the preview pane to copy the text. ## Find & Replace Tick the **Replace** checkbox to reveal the replace bar. Replace always operates on **target text only** – source text is never modified. | Action | Description | | --------------- | -------------------------------------------------------------------------------------------------------------------------------------- | | **Replace** | Replaces the match in the currently selected result. The segment must be in the active file – double-click it first to navigate there. | | **Replace All** | Replaces all target matches across all files. A confirmation dialog shows how many segments in how many files will be affected. | ### How Replace All works * For the **active file**: changes go through the Trados API, so they appear immediately and are tracked in Trados’s undo history. * For **other files**: the SDLXLIFF XML is modified directly on disk. You need to reopen those files to see the changes. Caution **Replace All cannot be undone** for files modified on disk. Always review the search results carefully before replacing. Consider saving your project first. ### Matches that span inline tags are skipped Trados segments often contain inline tags – formatting marks, placeholders, field codes – that interrupt a run of plain text. If your search string would only match across one of these tag boundaries (for example, searching for `important thing` when the segment renders as `importantthing`), Replace and Replace All will **skip that segment** rather than apply a destructive flatten-and-rewrite that would lose the tag. You’ll see this in the status bar after a Replace All as `…, skipped N (match spans inline tags)`. The skipped segments are left untouched so the formatting survives; you can edit them manually if you want the replacement to happen. This applies to both the active-file path (Trados API replacements) and the on-disk path (SDLXLIFF XML rewrites). It only kicks in when the match genuinely straddles a tag – ordinary matches inside a single text run are replaced normally and tags are preserved. ## Regex Tips When the **.\*** checkbox is enabled, the search query is treated as a .NET regular expression. Some useful patterns: | Pattern | Matches | | ---------------- | --------------------------------------------------- | | `\bword\b` | ”word” as a whole word (not “keyword” or “wording”) | | `(word1\|word2)` | Either “word1” or “word2” | | `\d+` | One or more digits | | `"[^"]*"` | Anything inside double quotes | | `\s{2,}` | Two or more consecutive whitespace characters | ## Keyboard Shortcuts | Shortcut | Action | | ----------------------------- | --------------------------------------------- | | **Alt+S** | Open SuperSearch (with selected text, if any) | | **Alt+W** | Search the web for the selected term | | **Enter** (in search box) | Start search | | **Enter** (in results grid) | Navigate to selected segment | | **Double-click** (result row) | Navigate to selected segment | ## Tips * Select a term in the editor and press **Alt+S** to instantly search for it across the entire project – or **Alt+W** to look it up on IATE, Linguee, Reverso and the rest, in your project’s language pair. * Use **Source only** scope to find segments where a particular term appears, then check how it was translated across files. * Use **Target only** scope with Replace to fix a consistent mistranslation across the entire project. * Use the **Files** and **TMs** buttons to limit the search to specific files or translation memories – useful in large projects where you only want to search a subset. * Switch the mode dropdown to **TMs** to use SuperSearch as a concordance tool, **Termbases** to search your terminology, or **Everything** to see project, TM and termbase hits side by side. * The status bar shows the number of results, what was searched, and the search time in milliseconds. * You can resize columns by dragging the column header borders. ## See Also * [Supervertaler](/trados/ai-assistant/) – AI-powered chat and context * [Batch Operations](/trados/batch-operations/) – Batch translate and proofread * [Keyboard Shortcuts](/trados/keyboard-shortcuts/) – All shortcuts in one place # Support There are several ways to get help with Supervertaler for Trados. *** ## GitHub Discussions [GitHub Discussions](https://github.com/orgs/Supervertaler/discussions) is the main community hub for both Supervertaler for Trados and Supervertaler Workbench. It is the best place to: * Ask questions and get help from other users * Share tips, workflows, and best practices * Suggest features and improvements * Discuss anything related to Supervertaler *** ## Bugs & Feature Requests Use [GitHub Issues](https://github.com/Supervertaler/Supervertaler-for-Trados/issues) to report bugs or request new features. When reporting a bug, please include: * Your Trados Studio version * The Supervertaler plugin version * Steps to reproduce the problem * Any error messages or screenshots *** ## Email For private enquiries, contact . # Termbase Management Supervertaler for Trados uses the same SQLite termbase format as Supervertaler Workbench. You manage your termbases through the Settings dialogue. ## Accessing termbase settings 1. Click the **gear icon** in the TermLens panel, or go to **Settings** in the plugin ribbon 2. Switch to the **TermLens** tab ## Database file The plugin stores all termbases in a single `.db` file (SQLite database). * Click **Browse** to select an existing database file * Click **Create New** to create a fresh, empty database ## MultiTerm termbases If your Trados project has MultiTerm termbases (`.sdltb` files) attached, they appear automatically at the bottom of the termbase list with a **\[MultiTerm]** label and green background. These termbases are read-only in TermLens –to manage their terms, use Trados’s built-in MultiTerm interface. See [MultiTerm Support](/trados/multiterm-support/) for full details. ## Termbase list Once a database is loaded, the termbase list shows all Supervertaler termbases it contains, plus any detected MultiTerm termbases. Each Supervertaler termbase has three toggles: | Toggle | Purpose | | ----------- | ----------------------------------------------------------------------------------------------- | | **Read** | Load terms from this termbase for matching in TermLens | | **Write** | New terms added via [quick-add shortcuts](/trados/termlens/adding-terms/) go into this termbase | | **Project** | Designate as the project termbase (terms shown in pink, prioritised in matching) | Caution Only one termbase can be marked as **Project** at a time. Setting a new project termbase clears the flag from the previous one. ## Creating a new termbase 1. Click **Add Termbase** 2. Enter a **name** for the termbase 3. Select the **source language** and **target language** 4. Click **OK** The new termbase appears in the list, ready for use. ## Import from TSV You can import terminology from a tab-separated values file: 1. Select the target termbase in the list 2. Click **Import from TSV** 3. Select your `.tsv` file 4. A column-mapping dialog opens (from v18.20.187): one row per column in the file, with a sample of its contents and a dropdown saying which termbase field it goes to. It is pre-filled from the file’s headers, so a file exported by Supervertaler needs no changes – check the row count, termbase name and language pair in the heading, and click **Import**. For a file with no language headers, or with the target column first, set the source and target yourself; any column you do not want goes to *ignore* 5. A progress bar tracks the import (useful for large termbases with thousands of terms) If the file’s languages are the other way round from the termbase, or are not its pair at all, the dialog says so in a note under the grid. The mapping it suggests already accounts for a reversed file.  The column-mapping dialog, here on a Supervertaler export: every column recognised, the two language columns mapped to source and target. Each line is one column of the file; Row 1 to Row 3 show what that column holds. **File format:** The first row must be a header row. Headers the dialog recognises on its own (case-insensitive) – anything else can still be mapped by hand: | Column | Required | Recognised headers | | ---------- | -------- | -------------------------------------------------------------------- | | **Source** | Yes | `Source`, `Source Term`, `Src`, or a language name (e.g., `English`) | | **Target** | Yes | `Target`, `Target Term`, `Tgt`, or a language name (e.g., `Dutch`) | | Term UUID | No | `Term UUID`, `UUID`, `Term ID`, `ID` | | Priority | No | `Priority`, `Prio`, `Rank` | | Domain | No | `Domain`, `Subject`, `Field`, `Category` | | Definition | No | `Definition` | | Notes | No | `Notes`, `Note`, `Comment`, `Description` | | Project | No | `Project` | | Client | No | `Client`, `Customer` | | Forbidden | No | `Forbidden`, `Do not use` | For terms with multiple synonyms, use pipe-delimited values: `main|synonym1|synonym2`. Forbidden synonyms are wrapped as `[!term]`. **Example:** ```plaintext Source Target Domain Notes database databank|gegevensbank software software Non-translatable user interface gebruikersinterface|gebruikersomgeving IT ``` ## Export To export all terms from a termbase: 1. Select the termbase in the list 2. Click **Export** 3. Pick the format in the save dialog, then choose a location Three formats, for three different purposes. ### TSV – the one that comes back unchanged Tab-separated columns with a header row: `Term UUID`, `Source`, `Target`, `Priority`, `Domain`, `Notes`, `Project`, `Client`, `Forbidden`. Synonyms are pipe-delimited and forbidden synonyms are marked with `[!term]`. UTF-8 with BOM, for Excel compatibility. Use it for a backup, for editing in a spreadsheet, or for moving terms between Supervertaler termbases – it reimports here with nothing lost. ### MultiTerm XML – for Trados The format MultiTerm and Glossary Converter import. This is how you get terms *out* of Supervertaler and into a Trados termbase: * **For a `.sdltb`**: convert the XML with Glossary Converter, or import it in MultiTerm. * **For a `.ttb`** (Studio 2026): in Studio’s **Termbases** view, create a termbase and use **Import Terms**. Carries source and target terms with their synonyms, plus definition, domain, notes, context, part of speech, URL, client, project and the forbidden flag – more than the TSV export, which has no column for several of those. ### TBX – for everything else TBX-Basic (ISO 30042), the standard interchange format. MultiTerm reads it and so do most other CAT tools, so it is the better choice if your terminology has to travel beyond Trados. ### What a round trip keeps, and what it doesn’t Terms, synonyms and the descriptive fields survive a full circle out to a Trados termbase and back. The *structure* does not: a MultiTerm entry is concept-oriented and can hold many languages, while a Supervertaler termbase is bilingual rows – so one conversion handles one language pair, and concepts flatten to pairs with any extra terms in a language becoming synonyms. ## Import from a Trados termbase **Import .sdltb/.ttb…** copies terms *out of* a Trados termbase and *into* a Supervertaler one. You choose the language pair, whether to create a new Supervertaler termbase or add to an existing one, and which of the Trados descriptive fields map to definition, domain, notes and so on. The Trados termbase is only ever read, never modified. An AI assistant connected through the [MCP server](/trados/mcp-server/) can do the same in one step with `import_project_termbase`, including a dry run that reports what would be imported before anything is written. ## Termbase Editor For full editing capabilities, double-click a termbase in the list to open the **Termbase Editor**. From here you can: * **Search** for terms by source or target text * **Edit** individual term entries * **Delete** terms * Perform **bulk operations** (e.g. bulk delete, bulk reverse) ### Right-click menu Right-clicking any row in the grid opens a context menu with the following actions: * **Copy cell** – copies the content of the clicked cell to the clipboard. * **Edit term…** – opens the full term entry editor for the clicked row. * **Reverse source/target** – swaps the source and target for the selected rows (see below). * **Delete term** – deletes the selected rows after confirmation. Multi-row selection is preserved: if you select several rows first and then right-click on one of them, the selection stays intact so actions apply to all selected entries. If you right-click on a row that wasn’t already selected, the selection collapses to just that row. ### Reversing source/target If you have term entries that ended up in the wrong direction – for example, English text in the Dutch column when the termbase is declared English → Dutch – you can correct them with **Reverse source/target**: 1. Select one or more rows in the grid (Shift-click or Ctrl-click for multi-select). 2. Right-click → **Reverse source/target (N entries)**. 3. Confirm. The operation swaps the source and target text, language tags, abbreviations, and flips the direction of every linked synonym. It runs in a single database transaction, so a partial failure leaves the termbase untouched. This action is mostly for repairing legacy entries created or edited under v4.19.24 or earlier, when the term entry editor could write values into the wrong DB columns in projects whose direction was the inverse of the termbase’s. From v4.19.25 onwards the editor guards against that, so new entries should not need this repair. ## Sharing termbases Caution **Mac users (Parallels):** On a Mac, Supervertaler Workbench runs natively on macOS while the Trados plugin runs inside Parallels (Windows). The two products cannot share the same `.db` file directly because the Trados plugin must store its data on the Windows side (`C:\Users\...`) – not on the Mac-side shared folder (`\\Mac\Home\...`). To keep your termbases in sync, export from one side and import on the other after making changes. This is a limitation of Parallels’ virtual network filesystem, not of the termbase format itself. *** ## See Also * [MultiTerm Support](/trados/multiterm-support/) * [TermLens Settings](/trados/settings/termlens/) * [Adding & Editing Terms](/trados/termlens/adding-terms/) * [Data Folder](/trados/data-folder/) # TermLens TermLens is an inline terminology display that shows the source text of the current segment word by word, with termbase translations directly underneath each matched term. It updates automatically when you navigate to a new segment.  ### How It Works When you select a segment in the Trados editor, TermLens analyses the source text against all active termbases and displays the result in a visual layout: * **Matched words** appear with their termbase translation underneath, on a coloured background * **Unmatched words** are shown in light grey text so you can read the full source sentence in context This gives you an at-a-glance overview of every term in the segment that has a termbase entry – without hovering or clicking anything. #### Selection tracking Selecting text in the editor’s **source segment** highlights the corresponding words in TermLens with a soft yellow band – matched and unmatched words alike. On a long segment this anchors your eye to the part you are actually working on, with the relevant term chips right there. The highlight follows your selection live and clears when you deselect. When the same phrase occurs more than once in a segment, the occurrence nearest your cursor is highlighted.  Select text in the source segment and TermLens highlights the same words – your eye lands straight on the relevant term chips. Selecting text in the **target segment** works in reverse: the term chips whose translation your selection covers light up, including matches via target synonyms and abbreviations. Only chips can light up from a target selection – the editor provides no word alignment between source and target, so unmatched words have no reliable counterpart to point at. Whichever side you selected last drives the highlight. ![]() ### Colour Coding TermLens uses five background colours to distinguish term types: | Colour | Meaning | | ---------- | ----------------------------------------------------------------------- | | **Blue** | Regular Supervertaler termbase match | | **Purple** | Abbreviation match (matched via source abbreviation, not the full term) | | **Pink** | Project termbase match (higher priority) | | **Yellow** | Non-translatable term (source = target) | | **Green** | MultiTerm termbase match (`.sdltb`) | ### Chip Indicators In addition to colour coding, TermLens shows small indicators in the top-right corner of term chips: | Indicator | Meaning | | -------------- | ----------------------------------------------------------------------------------- | | **≡** (indigo) | The entry has synonyms (source-side, target-side, or both). Hover to see them. | | **●** (amber) | The entry has metadata – a definition, domain, notes, or URL. Hover to see details. | Both indicators can appear simultaneously. Hover over any term chip to see an interactive popup with full details, including source synonyms (prefixed with “Also:”), target synonyms (shown as bullet points), definitions, domain, notes, and clickable URLs. The popup stays open when you move the mouse into it, so you can click on links. #### Markdown Rendering The **Notes** and **Definition** fields in the term popup support Markdown formatting. If the content contains Markdown syntax (tables, bold, italic, headings, bullet lists, code blocks), it is rendered with proper formatting instead of plain text. This is especially useful when AI-generated term notes include structured data like translation tables. ![]() Markdown formatting rendered in TermLens term popup #### Resizable Popup You can resize the term popup by dragging the grip in the bottom-right corner. The width is remembered for the rest of the session, so subsequent popups open at your preferred size. ### Inserting Terms #### Click to Insert Click any translation shown under a source word. The translation is inserted at the cursor position in the target field. #### Automatic capitalisation Displayed and inserted terms follow the capitalisation of the source occurrence in the segment, not the capitalisation stored in the termbase. A term stored as “More preferably” shows and inserts as “more preferably” when the segment contains it lower-case mid-sentence; a lower-case stored term is capitalised when the occurrence starts the sentence; and an ALL-CAPS occurrence (a heading, say) upper-cases the whole term. This applies to every insertion path – chip clicks, Alt+digit shortcuts, the TermLens popup and TermPicker. The rules are deliberately conservative: acronyms and mixed-case terms (MRI, pH) are never altered, and abbreviation matches keep their stored casing. You can switch the behaviour off with **Adapt term capitalisation to the segment** in [TermLens settings](/trados/settings/termlens/#adapt-term-capitalisation). #### Keyboard Shortcuts (Alt+1 through Alt+9) Each matched term in TermLens is assigned a **numbered badge**. Press **Alt+1** to insert the first match, **Alt+2** for the second, and so on up to **Alt+9**. #### Shortcuts for Terms 10+ For terms numbered 10 and above, TermLens supports two shortcut styles (configurable in Settings): * **Sequential** (default) – type the term number digit by digit: `Alt+14` inserts term 14 * **Repeated digit** – press the same digit key multiple times: `Alt+55` inserts term 14 (5th term in the second tier: 9+5) The badge on each term chip shows exactly which key combination to use. See [Keyboard Shortcuts](/trados/keyboard-shortcuts/) for details on both modes. #### TermLens popup (Alt+L) Press **Alt+L** to open the [**TermLens popup**](/trados/termlens/termlens-popup/) – a borderless floating version of this panel for the active segment. Designed for keyboard-only term selection on small screens where keeping the docked panel always-visible costs too much vertical space. Press **Alt+L** again to close. Inside, **Right / Down / Tab** cycle the highlighted match, **Enter** inserts and closes, **Escape** dismisses without inserting. #### TermPicker (Alt+P) For segments with many matches and when a sortable list view is preferable, press **Alt+P** to open [**TermPicker**](/trados/termlens/termpicker/). It shows all matched terms in a list – synonyms expanded – and lets you insert any term with a double-click or Enter. TermPicker is a sibling surface to TermLens: same termbase data, different ergonomics (flat list vs in-context chips). TermPicker is also available as a **dockable pane** (Studio’s **View** tab → **TermPicker**), so you can keep the list permanently visible instead of the TermLens panel if that suits you better. Both views are available in both placements – docked or as a popup at the cursor.  ### Right-Click Context Menu Right-click any term in TermLens to access: | Action | Description | | ---------------------------- | ---------------------------------------------------------------------------------- | | **Edit Term** | Open the term editor to modify source, target, or metadata | | **Delete Term** | Remove the term from the termbase | | **Mark as Non-Translatable** | Flag the term so it appears in yellow (source = target) | | **Mark as Translatable** | Remove the non-translatable flag (shown when the term is already non-translatable) | ### Quick-Add Terms You can add terms without opening a dialogueue: | Shortcut | Action | | -------------- | ---------------------------------------------------------------------------------------- | | **Alt+Down** | Quick-add the selected text to all write termbases | | **Alt+Up** | Quick-add the selected text to the project termbase | | **Ctrl+Alt+T** | Open the Add Term Entry dialogue (full editor: definition, domain, notes, URL, synonyms) | | **Ctrl+Alt+N** | Quick-add the selected text as a non-translatable term | ### Font Size Use the **A+** and **A-** buttons in the TermLens panel header to increase or decrease the font size. Changes apply immediately. ### Tips * TermLens respects termbase activation –only terms from activated termbases are shown. * If you have many termbases, designate one as the **Project termbase** (shown in pink) to make its terms stand out. * Hover over a term to see an interactive popup with all translations, synonyms, abbreviation pairs, definitions, URLs, and the termbase name. The popup stays open when you move the mouse into it, allowing you to click on URLs. * A small **indigo ≡ indicator** appears in the top-right corner of a term chip when the entry has synonyms. An **amber dot** appears when the entry has metadata (definition, domain, notes, or URL). Both indicators can appear together. * If a term has an **abbreviation** (e.g., “GC” for “gaschromatografie”), both the full term and the abbreviation are highlighted when they appear in the same segment. The abbreviation chip shows the abbreviated translation; the full-term chip shows the full translation. *** ### See Also * [Adding & Editing Terms](/trados/termlens/adding-terms/) * [TermPicker](/trados/termlens/termpicker/) * [MultiTerm Support](/trados/multiterm-support/) * [Keyboard Shortcuts](/trados/keyboard-shortcuts/) * [Getting Started](/trados/getting-started/) # Adding Terms Supervertaler for Trados provides several ways to add, edit, and manage terminology without leaving the Trados editor. ## Quick-add (Alt+Down) The fastest way to add a term while translating: 1. Select the **source text** you want to add as a term 2. Select the **target text** (the translation) 3. Press **Alt+Down** The term is added instantly to all **write-enabled** termbases. No dialogue, no interruption. ## Quick-add to project termbase (Alt+Up) Works the same as Alt+Down, but adds the term specifically to the **project termbase** (the termbase marked as “Project” in settings). Use this when you want to keep client-specific terminology separate and prioritised. 1. Select the **source text** 2. Select the **target text** 3. Press **Alt+Up** ## Quick-add non-translatable (Ctrl+Alt+N) For terms that should remain identical in source and target (brand names, product codes, abbreviations): 1. Select the text in the **source** field 2. Press **Ctrl+Alt+N** This creates a term entry where source and target are the same. Non-translatable terms appear as **yellow** chips in [TermLens](/trados/termlens/), the [TermLens popup](/trados/termlens/termlens-popup/) and [TermPicker](/trados/termlens/termpicker/). ## Add term with abbreviation (Ctrl+Alt+A) When a segment spells a concept out in full **and** gives its abbreviation, this fills the dialogue in for you. Take a segment like: > Deze verklaring wordt opgesteld conform de **Sustainable Finance Disclosure Regulation** (**SFDR**, Verordening (EU) 2019/2088). Press **Ctrl+Alt+A** (or right-click → **Add term with abbreviation (AI)**) and the **Add term entry** dialogue opens with the source term, the target term and both **Abbreviation** fields already filled in. Check them and click **Add**. 1. Optionally select any part of the term you want 2. Press **Ctrl+Alt+A** 3. Review the pre-filled dialogue and click **Add** **Your selection decides which term.** Select any part of a term – or a whole phrase containing it – and that is the term you get, completed to its full extent. The AI works out where the term begins and ends and finds its abbreviation; it will not swap in a different term. With nothing selected, it looks at the whole segment. Caution Nothing is saved until you click **Add**. Do check the fields – the AI is restricted to copying text that genuinely appears in the segment and can never invent an abbreviation, but it can still pick a wider or narrower span than you had in mind. Requires an AI provider configured in [AI Settings](/trados/settings/ai-settings/); it uses whichever provider and model you have selected. ## Add term entry (Ctrl+Alt+T) For full control over a new term, press **Ctrl+Alt+T** (or right-click in the editor and choose **Add Term…**). This opens the **Add term entry** dialogue, which lets you fill in all fields before saving: | Field | Description | | ----------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Source** | The source-language term | | **Target** | The target-language translation | | **Source Abbreviation** | Optional abbreviated form (e.g. “GC” for “gaschromatografie”). Separate multiple variants with `\|`. | | **Target Abbreviation** | Optional abbreviated form of the target term | | **Source synonyms** | Alternative source-language forms for the same concept | | **Target synonyms** | Alternative target-language translations | | **Definition** | Optional definition or usage note. Supports multiple lines – click the **▼** button to expand the field for longer content. | | **Domain** | Subject area (e.g. “Legal”, “Patents”, “Medical”) | | **Notes** | Any additional notes for translators. Supports multiple lines with an expand button, like Definition. | | **URL** | Optional reference URL (shown as a clickable link in the term popup) | | **Client** | Optional client code (e.g. “ACME”, “GLOBEX”). A label for your own filtering and reporting. It no longer selects SuperMemory content: the bank you pick in the toolbar is what the AI reads. | | **Project** | Optional project name (e.g. a job code or client-side project ID). Bookkeeping field for the user’s own organisation – not sent to the AI in translation prompts. The Termbase Editor’s grid lets you sort and filter by Project. | | **Non-translatable** | Check this to mark the term as non-translatable | The term is added to the **project termbase** if one is configured, or the first write-enabled termbase otherwise. Caution **Trados conflict:** Trados Studio assigns **Ctrl+Alt+T** to “Insert TM Symbol” by default. If pressing Ctrl+Alt+T does nothing, you need to remove Trados’s binding first. Go to **File → Options → Keyboard Shortcuts**, search for “Insert TM Symbol”, and delete or reassign its shortcut. Then Ctrl+Alt+T will work as expected in Supervertaler. ## Smart selection You don’t need to precisely select entire words when adding terms. All quick-add shortcuts (**Alt+Down**, **Alt+Up**, **Ctrl+Alt+N**, **Ctrl+Alt+T**) automatically expand your selection to the nearest word boundaries. For example, to add **standalone version** = **zelfstandige versie** to your termbase, it’s enough to select **alone ver** in the source and **andige ver** in the target. Supervertaler expands both selections to the full words automatically. This means you can work fast and loose with your mouse or keyboard selections – no need for the precise click-and-drag that normally slows you down. Just grab roughly the right area and Supervertaler takes care of the rest. ### How it works When you make a selection, Supervertaler scans the full segment text for every occurrence of your selected text and applies these rules, in order: 1. **Exact word match wins** – if the selection matches a complete word somewhere in the segment (i.e. it sits between spaces or punctuation), that word is used as-is. For example, if the segment contains both *hechtingsbevorderaars* and *hechting*, selecting **hechting** returns **hechting** – the exact word – not the longer compound. 2. **Shortest word wins** – if the selection is embedded inside multiple words, the shortest enclosing word is preferred. For example, if the segment contains *hechtingsbevorderaars* and *hechting*, selecting **echt** returns **hechting** (8 characters) rather than *hechtingsbevorderaars* (21 characters), because the user most likely intended the simpler word. 3. **Single match expands** – if the selection appears inside only one word, it expands to that word’s boundaries. ### Tips for reliable results * **Select at least 3–4 characters** – very short selections (1–2 characters) may match common short words elsewhere in the segment (e.g., selecting **he** could match the word *the*) * **Select the whole word when in doubt** – if a segment contains similar-looking words and you want a specific one, a complete-word selection is always matched correctly * **Use Ctrl+Alt+T for tricky cases** – the Add Term Entry dialogue lets you review and edit the expanded term before saving, so you can catch any unexpected expansion ## Merge prompt When you add a term and the **source** or **target** already exists in the termbase (but with a different translation), Supervertaler shows a prompt asking what you want to do: * **Add as Synonym** – merges the new translation into the existing entry as a synonym, keeping your termbase tidy * **Add & Edit…** – adds the synonym and opens the Term Entry Editor so you can review the metadata before saving * **Keep Both** – creates a separate entry alongside the existing one * **Cancel** – aborts the operation The merge prompt always displays terms in your **project’s language direction**, regardless of how the termbase stores them internally. For example, in a Dutch → English project using an English → Dutch termbase, the dialogue shows the Dutch source term first and the English target term second. **Example:** Your termbase already has **adhesion → hechting**. You select **adhesion → aanhechting** and press Alt+Down. The merge prompt appears because the source term “adhesion” already exists. Clicking “Add as Synonym” adds *aanhechting* as a target synonym of the existing entry, so both translations are grouped together. ## Editing existing terms To edit a term that already exists in your termbase: 1. Right-click the term in the **TermLens** panel 2. Select **Edit Term…** 3. The **Term Entry Editor** opens, where you can: * Modify the source or target text * Add or remove **synonyms** (multiple translations for one source term) * Update the definition * Toggle the non-translatable flag Click **Save** when done. ## Abbreviations Term entries can have optional **source and target abbreviation** fields. When a source abbreviation appears in a segment, TermLens highlights it and shows the target abbreviation underneath – just like a regular term match. ### Adding abbreviations 1. Open the **Term Entry Editor** (right-click a term → Edit Term) 2. Fill in the **Source Abbreviation** and **Target Abbreviation** fields 3. Click **Save** ### Multiple abbreviation variants You can specify multiple variants of the same abbreviation by separating them with a **pipe character** (`|`): ```plaintext GC|G.C.|gc|g.c. ``` Each **source** variant is indexed and matched independently, so all common forms of the abbreviation are recognised in the source text. The **first variant** is used as the display text and for insertion. ### How abbreviation matching works When both the full term and its abbreviation appear in the same segment (e.g., “gaschromatografie (GC)”), TermLens shows **both** as highlighted chips: * The **full term** chip shows the full target translation (e.g., “gas chromatography”) – displayed in the regular **blue** colour * The **abbreviation** chip shows the target abbreviation (e.g., “GC”) – displayed in **lavender** so it is instantly distinguishable from a full-term match Clicking or Alt+digit-inserting an abbreviation chip inserts the **target abbreviation** (first variant), not the full target term. ## Deleting terms 1. Right-click the term in the **TermLens** panel 2. Select **Delete Term** 3. Confirm the deletion in the dialogue Caution Deletion is permanent. The term is removed from the termbase database file. ## Bulk Add Non-Translatable For adding many non-translatable terms at once (e.g., a list of brand names or product codes): 1. Open **Settings** (gear icon in the TermLens panel) 2. Find the **Bulk Add Non-Translatable** option 3. Paste your terms, **one per line** 4. Click **Add** to save them all at once *** ## See Also * [TermPicker](/trados/termlens/termpicker/) * [Termbase Management](/trados/termbase-management/) * [TermLens Settings](/trados/settings/termlens/) # TermLens popup The **TermLens popup** is a borderless floating version of the docked TermLens panel for the active segment. Designed for keyboard-only term selection on small screens – and for translators who want to insert terms without ever reaching for the mouse.  The TermLens popup with the current match highlighted (amber ring on the source word) ### When to use it * **Small screens / laptops** – keeping the docked TermLens panel always-visible can cost too much vertical space, especially for longer source sentences. The popup gives you the same view on demand and disappears when you’re done. * **Pure-keyboard workflows** – Alt+L, cycle, Enter, back to typing. No mouse, no menu hunting. ### Opening and closing | Key | Action | | ----------------------- | ------------------------------------------------ | | **Alt+L** | Toggle the popup (open if closed, close if open) | | **Escape** | Close without inserting | | Click outside the popup | Close without inserting | You can change the key in **File → Options → Keyboard Shortcuts**. (Earlier versions listed **Ctrl+Alt+G**; that key now belongs to [AutoTagger](/trados/autotagger/).) **Was a Ctrl tap until this version.** Pressing and releasing Ctrl on its own used to open the popup – a quick gesture, but not one Studio could tell apart from any other program’s Ctrl-modified shortcut once something else had consumed the middle key. The popup opened by itself for anyone running a keyboard tool, a text expander or voice commands alongside Studio. Alt+L is unambiguous. If you preferred the tap, note that Studio remembers per-user shortcuts, so an existing installation keeps whatever you already had bound. ### Cycling between matches When the popup opens, the first match has an amber ring around its source word – that is the **current match** that Enter will insert. | Key | Action | | --------------------------------- | -------------------------------------------------- | | **Right** / **Down** / **Tab** | Move the current-match highlight to the next match | | **Left** / **Up** / **Shift+Tab** | Move it to the previous match | Cycling wraps: from the last match, Right takes you back to the first. ### Inserting | Key / action | Result | | ------------------ | -------------------------------------------------------------------------------------------------- | | **Enter** | Insert the current match into the target segment, close the popup, return focus to the target cell | | **Click any chip** | Insert that match into the target segment, close the popup, return focus to the target cell | Both paths share the same insertion logic – there is no difference between picking by keyboard and picking by mouse. ### Editing a match Press **E** while a match is highlighted to open the term-entry editor for that entry. The popup closes first so the editor opens with clean focus. The editor is the same dialogue the docked panel’s right-click “Edit Term…” menu uses, including the multi-termbase editing case for entries that exist in more than one termbase. ### Visuals The popup uses the same chip rendering, colour scheme, and metadata indicators as the docked TermLens panel – pink for project termbase terms, blue for regular Supervertaler terms, yellow for non-translatable, green for MultiTerm. See the [TermLens overview](/trados/termlens/) for the full colour key. ### TermLens popup vs TermPicker Both show the same matches for the active segment. Pick whichever fits your style: | | TermLens popup (Alt+L) | [TermPicker](/trados/termlens/termpicker/) (Alt+P, or docked) | | -------- | ------------------------------------------------------ | ------------------------------------------------------------- | | Layout | Source segment with chips underneath each matched word | Sortable, scrollable table | | Best for | Skimming matches in segment context | Many matches that benefit from sorting / typing-to-jump | | Keyboard | Arrow / Tab cycles a highlighted match | 0–9 jumps directly; Up / Down navigate | | Modality | Modeless – click outside to dismiss | Modal – Escape or Cancel to close | *** ### See Also * [TermLens overview](/trados/termlens/) * [TermPicker](/trados/termlens/termpicker/) * [Keyboard shortcuts](/trados/keyboard-shortcuts/) # TermPicker **TermPicker** shows all matched terms for the current segment as a sortable, keyboard-navigable list. It is useful when [TermLens](/trados/termlens/) shows many matches and you want a quick overview without scrolling – and it is available either as a popup at your cursor or as a permanently docked pane.  TermPicker with all matched terms for the current segment ### Two views, two placements TermLens and TermPicker are sibling surfaces: both show the terminology matches for the current segment, drawn from the same termbases, but they present them differently. Each is available in both placements, so you can choose the **view** you prefer independently of **where** you want it: | | Docked pane | Popup at the cursor | | -------------- | --------------- | ------------------- | | **TermLens** | TermLens panel | tap **Ctrl** | | **TermPicker** | TermPicker pane | **Alt+P** | * **TermLens** shows matches *in context* – the source sentence with terms highlighted in place. Best for reading and scanning. * **TermPicker** shows the same matches as a flat sortable list. Best for quick insertion and for seeing every synonym at once. ### Opening TermPicker **As a popup:** press **Alt+P**. It appears above the editor with every synonym group already expanded, so you can see all alternatives at a glance. **Escape** closes it. **As a docked pane:** open it from Studio’s **View** tab → **TermPicker**. The pane stays visible and updates as you move through the document, in step with the TermLens panel. Drag it wherever suits you – Studio remembers the position. A layout that works well is the Translation Results window at the top right with the TermPicker pane directly below it. ### Colour-coded rows Each row in TermPicker is colour-coded by termbase type: | Colour | Meaning | | ---------- | ----------------------------------- | | **Pink** | Project termbase term | | **Blue** | Regular Supervertaler termbase term | | **Yellow** | Non-translatable term | | **Green** | MultiTerm termbase term (`.sdltb`) | This lets you instantly see where each term comes from and how it should be handled. ### The details dot An **amber dot** in the second column marks terms that carry extra information – a definition, domain, notes or a URL. Press **I** on such a row to see it (see below). Rows without a dot have nothing further to show, so you never have to guess. This mirrors the dot on the [TermLens](/trados/termlens/) chips. ### Expandable synonyms Terms with multiple translations open **already expanded**, with their alternatives listed as sub-rows beneath the term, so nothing is hidden behind a marker. Press **Left arrow** to collapse a group (the indicator changes to **▸**) and **Right arrow** to expand it again. ### Keyboard navigation TermPicker is designed for fast keyboard use, and the keys are identical in the popup and the pane: | Key | Action | | ------------- | ------------------------------------------------------------------ | | **Up / Down** | Navigate between rows (wraps around) | | **Right** | Expand synonyms for the selected term | | **Left** | Collapse synonyms | | **0-9** | Jump directly to that term number | | **I** | Show the term’s details – definition, domain, notes, URL, synonyms | | **E** | Open the term editor for the selected term | | **Enter** | Insert the selected term | | **Escape** | Close the popup without inserting | Navigation wraps around: pressing **Down** on the last row jumps to the first, and **Up** on the first jumps to the last. ### Term details (I) Pressing **I** on a row opens a small window just below it showing everything the termbase holds for that term: its synonyms, definition, domain, notes and URL, for every entry behind the row. Press **I** again – or **Escape** – to dismiss it. It also closes by itself when you move to another row, so it can never describe the wrong term. ### Right-click menu Right-clicking a row gives you the same three actions as right-clicking a TermLens chip: | Action | Effect | | ---------------------------- | -------------------------------------------------------- | | **Edit Term…** | Opens the term editor (also **E**) | | **Mark as Non-Translatable** | Flags the term so source = target (or removes the flag) | | **Delete Term** | Removes the term from the termbase, after a confirmation | MultiTerm terms are read-only in Supervertaler, so these actions are greyed out for them – edit those in Trados’s own MultiTerm interface. ### Inserting a term You can insert a term in two ways: * **Double-click** any row to insert that term at the cursor position in the target field * **Press Enter** on the selected row From the popup, inserting also closes it; from the docked pane, the list stays open so you can insert several terms in a row. Like the TermLens chips, the picker displays and inserts terms with the capitalisation of the segment occurrence (the first occurrence when a term appears more than once) rather than the stored capitalisation – see [Adapt term capitalisation](/trados/settings/termlens/#adapt-term-capitalisation). *** ### See Also * [TermLens](/trados/termlens/) * [TermLens popup](/trados/termlens/termlens-popup/) * [Adding & Editing Terms](/trados/termlens/adding-terms/) * [Keyboard Shortcuts](/trados/keyboard-shortcuts/) * [Termbase Management](/trados/termbase-management/) # Replace curly quotes with straight quotes Text transforms are a special type of QuickLauncher prompt that performs local find-and-replace operations on the active target segment – instantly, without calling an AI provider. ## When to use text transforms Text transforms are useful for cleaning up invisible or problematic characters in your translations. For example: * **InDesign (IDML) forced line breaks** – InDesign uses invisible Unicode LINE SEPARATOR (U+2028) characters as forced line breaks (Shift+Enter). These are invisible in Trados but can cause problems in your translations. * **Zero-width spaces and joiners** – invisible characters from PDF or web sources * **Normalising quotes or dashes** – replacing curly quotes with straight quotes, or em dashes with en dashes ## How it works 1. Navigate to the segment you want to clean 2. Press **Alt+Q** (or right-click → QuickLauncher) 3. Open the **Text operations** folder 4. Click **Strip U+2028** (or another transform) The transform runs instantly. A dialogue confirms how many replacements were made, and the cleaned text is copied to your clipboard. ## Built-in transforms Supervertaler ships with one built-in text transform: ### Strip U+2028 Removes invisible Unicode LINE SEPARATOR (U+2028) and PARAGRAPH SEPARATOR (U+2029) characters from the target segment, replacing them with spaces. Consecutive spaces are collapsed to a single space. These characters are commonly inserted by InDesign (IDML) as forced line breaks (Shift+Enter). They are invisible in the Trados editor but can corrupt translations – the AI may produce spurious line breaks, or the characters may cause formatting issues in the final document. ## Creating your own transforms Text transforms are stored as `.md` files in your prompt library, just like regular prompts. The only difference is the YAML frontmatter has `type: transform` instead of `type: prompt`, and the content body contains find/replace rules instead of a prompt. ### Step by step 1. Open **Settings → Prompts** 2. Click **New** 3. Set the **Category** to `QuickLauncher/Text operations` (or any QuickLauncher subfolder) 4. In the YAML frontmatter, change `type: prompt` to `type: transform` 5. In the content body, write your find/replace rules ### Rule format Each rule is a `find:` / `replace:` pair. Blank lines between rules are optional but improve readability. Lines starting with `#` are comments. ```plaintext find: "\u201C" replace: "\u0022" find: "\u201D" replace: "\u0022" ``` ### Unicode escapes Use `\uXXXX` to specify Unicode characters by their code point. This is essential for invisible characters that cannot be typed or seen in a text editor. | Escape | Character | Description | | -------- | ----------- | ------------------------------------------- | | `\u2028` | (invisible) | LINE SEPARATOR – InDesign forced line break | | `\u2029` | (invisible) | PARAGRAPH SEPARATOR | | `\u200B` | (invisible) | ZERO WIDTH SPACE | | `\u200C` | (invisible) | ZERO WIDTH NON-JOINER | | `\u200D` | (invisible) | ZERO WIDTH JOINER | | `\uFEFF` | (invisible) | BYTE ORDER MARK (BOM) | | `\u00A0` | (invisible) | NON-BREAKING SPACE | | `\u201C` | ” | LEFT DOUBLE QUOTATION MARK | | `\u201D` | ” | RIGHT DOUBLE QUOTATION MARK | ### Example: Strip U+2028 (built-in) ```yaml --- type: transform name: "Strip U+2028" description: "Removes invisible Unicode LINE SEPARATOR and PARAGRAPH SEPARATOR" category: "QuickLauncher/Text operations" default: true --- # Strip invisible Unicode line/paragraph separators. # These are commonly inserted by InDesign (IDML) as forced line breaks. find: "\u2028" replace: " " find: "\u2029" replace: " " ``` ### Example: Normalise non-breaking spaces ```yaml --- type: transform name: "Fix non-breaking spaces" description: "Replaces non-breaking spaces with regular spaces" category: "QuickLauncher/Text operations" --- # Replace non-breaking spaces (U+00A0) with regular spaces find: "\u00A0" replace: " " ``` ## Keyboard shortcuts Text transforms appear in the QuickLauncher menu alongside regular prompts. You can assign them to keyboard slots (Ctrl+Alt+1 through Ctrl+Alt+0) for instant access: 1. Open **Settings → Prompts** 2. Select the transform in the tree 3. Choose a **Shortcut** slot from the dropdown at the bottom ## Clipboard After a transform runs, the cleaned target text is automatically copied to your clipboard. This is useful if you need to paste the cleaned text elsewhere – for example, into a text editor or a QA tool. ## Technical notes * Transforms use Trados’s `ProcessSegmentPair` API to commit changes, the same mechanism used by Batch Translate. This ensures all formatting tags (bold, italic, etc.) are preserved. * After replacements, consecutive spaces are collapsed to a single space to prevent double spaces where an invisible character sat next to an existing space. * Transforms do not appear in the AI Assistant chat – they run locally and show a brief confirmation dialogue. *** ## See Also * [QuickLauncher](/trados/quicklauncher/) * [Prompts](/trados/settings/prompts/) * [Keyboard Shortcuts](/trados/keyboard-shortcuts/) # Troubleshooting Solutions to common issues with the Supervertaler for Trados plugin. *** ## Plugin not loading **Symptoms:** The TermLens panel does not appear in Trados Studio, or the plugin ribbon tab is missing. **Solutions:** 1. **Check Trados version** –the plugin requires **Trados Studio 2024** or later 2. **Verify .NET Framework** –ensure **.NET Framework 4.8** is installed on your system 3. **Reinstall the plugin** –remove the plugin via **Trados Plugin Management**, restart Trados, then install it again 4. **Check for errors** –open **Trados Plugin Management** and look for error messages next to the Supervertaler plugin entry *** ## The installer finishes, but the plugin never appears **Symptoms:** You install from the App Store, the Trados Plugin Installer runs through every step and reports success, and then Supervertaler is not in the **View** menu and not in **Plugin Management**. Reinstalling does exactly the same thing. Often the plugin was working before and disappeared on its own. This is the most common installation problem, and it has one cause far more often than any other. ### First: was Trados Studio really closed? **The installer fails silently if Studio is running.** Not with an error – it completes normally and reports success, having changed nothing that matters. Each install location holds the plugin twice: the package, and an **unpacked** folder that Studio loads from and holds open the whole time it is running. An installer that cannot replace the unpacked folder leaves the old one in place, and **Studio will not re-extract into an unpacked folder that already exists**. The result is a successful install that changes nothing – even with the cleanup checkbox ticked, because that cleanup cannot delete files that are in use either. So: 1. Close Trados Studio – **every** window, not just your project. 2. Open Task Manager (`Ctrl+Shift+Esc`), look under **Details** for **`SDLTradosStudio.exe`**, and end it if it is still there. Studio can take a few seconds to exit, and can occasionally linger after its windows have closed. 3. Run the installer again, leaving **“Remove this plugin from all installation folders”** ticked. 4. Start Studio. That is the whole fix in most cases. ### Second: is there more than one copy in the Packages folder? Look in the folder for your Studio version (full paths further down): ```plaintext ...\Trados\Trados Studio\19\Plugins\Packages\ ``` There should be **exactly one** file with Supervertaler in the name. If there are two, that is the problem, and it explains why reinstalling never helps. Both files declare themselves as the same plugin, so Studio finds two copies of one plugin and loads neither. And because each install only ever replaces the file it is named after, a second install lands beside the first rather than on top of it – the fault repairs itself only if you delete **both** by hand and then install once. This can happen if the plugin has reached your machine by more than one route: from the App Store, from a file sent to you directly, or from an earlier version whose file was named differently. Delete every Supervertaler file you find there, then install once from the App Store. ### Third: is your Studio version greyed out in the installer? On the installer’s first screen, the list of installed Studio versions greys out any version the plugin does not support: > Studio versions that are not compatible with the plugin will be grayed out. **Almost always this means you downloaded the other build.** Supervertaler for Trados ships as two separate downloads, and the App Store page asks which you want: > Trados Studio - 2026 Release, 19.x Trados Studio 2024, 18.x The 2024 build greys out Studio 2026, and the 2026 build greys out Studio 2024 – by design, since each is built against its own Studio. If the version you want is greyed out, go back to the [App Store page](https://appstore.rws.com/plugin/432), click **Download**, and pick the other entry from the dropdown. If you are certain you downloaded the right build and your Studio version is *still* greyed out, email with the version number from **Help → About**. That means your Studio is outside the range this build declares, which is a fault at our end, not yours. ### Fourth: is it installed but switched off? Open **Help → Plugin Management** and look for Supervertaler in the list. If it is there but disabled, or shows an error beside it, that is a different problem from a failed install – the entry’s error message is the thing to send us. ### Last resort: clean out every copy by hand Only needed if the steps above do not work. Close Studio, then paste each of these paths into the address bar of a File Explorer window and delete anything with **Supervertaler** in the name – a `.sdlplugin` file in the `Packages` folders, a folder in the `Unpacked` ones. Replace `` with your own Windows user name. Use the block for your Studio version – `18` is Studio 2024, `19` is Studio 2026. Each path is one of the three choices the Trados Plugin Installer offers under “Please select the folder where the plugin will be installed”, so if you remember which you picked, start with that one – but check all three, because an earlier install may have used a different one. **Trados Studio 2024** ```plaintext C:\Users\\AppData\Roaming\Trados\Trados Studio\18\Plugins\ <- "All your domain computers" (the default) C:\Users\\AppData\Local\Trados\Trados Studio\18\Plugins\ <- "This computer for me only" C:\ProgramData\Trados\Trados Studio\18\Plugins\ <- "This computer for all users" ``` **Trados Studio 2026** ```plaintext C:\Users\\AppData\Roaming\Trados\Trados Studio\19\Plugins\ <- "All your domain computers" (the default) C:\Users\\AppData\Local\Trados\Trados Studio\19\Plugins\ <- "This computer for me only" C:\ProgramData\Trados\Trados Studio\19\Plugins\ <- "This computer for all users" ``` Inside each one there are two folders that matter, and **both** need clearing: * `Packages` holds the installed `.sdlplugin` file. * `Unpacked` holds the files Studio actually loads, extracted from it. This is the one people miss, and it is the one that blocks a reinstall: Studio will not re-extract over an `Unpacked` folder that is already there. Several of these will not exist, or will contain nothing from Supervertaler. That is normal – move on to the next. Delete **every** copy you find, including any that look like the current version: a leftover that looks correct is exactly the kind that wins the race against the new install. Then start Studio once and close it again, so it writes out a plugin list with nothing from Supervertaler in it, and install once more. *** ## A keyboard shortcut does nothing **Symptoms:** A Supervertaler shortcut – e.g. `Alt+T` (translate segment), `Ctrl+Alt+T` (add term), `Ctrl+Alt+N` (non-translatable), `Ctrl+Alt+G` (AutoTagger), `Alt+Up` (quick-add to project termbase) or `Alt+Q` (QuickLauncher) – has no effect in the editor. **Solutions:** 1. **Clear the conflicting Trados default** – Trados Studio ships with its own actions bound to these key combinations, and the Trados binding wins. Go to **File → Options → Keyboard Shortcuts**, search for the conflicting Trados action, and delete its binding. The full table of what to delete is in [Keyboard Shortcuts](/trados/keyboard-shortcuts/#first-time-setup-free-up-trados-shortcuts) 2. **Repeat after a reinstall** – reinstalling or resetting Trados Studio restores its default bindings, so the shortcuts stop working again until you clear them once more *** ## ”Could not load SQLite” or DLL errors **Symptoms:** Error messages about missing DLLs or SQLite when opening settings or loading a termbase. **Solutions:** * **Restart Trados Studio** after the first install. The plugin pre-loads its own SQLite DLL to avoid conflicts with other plugins, but this requires a clean startup * If the error persists, reinstall the plugin to restore any missing DLL files *** ## Database locked / “cannot open database” **Symptoms:** Error when trying to load or write to the termbase database. **Solutions:** * **Close Supervertaler Workbench** if it has the same `.db` file open. Two applications writing to the same SQLite file simultaneously can cause lock conflicts * The plugin uses **read-only mode** where possible to minimise conflicts, but write operations (adding terms) require exclusive access * Verify the `.db` file is not on a drive that has gone offline (e.g., a disconnected network share) Caution If you share the database via a cloud-sync folder, ensure the file is fully synced before opening it in the plugin. Partially synced files can appear locked or corrupt. *** ## Terms not appearing **Symptoms:** TermLens shows no matches even though you know the segment contains terms that exist in your termbase. **Solutions:** 1. **Check the Read toggle** –open [TermLens Settings](/trados/settings/termlens/) and verify the termbase has **Read** enabled 2. **Verify the database path** –ensure the path points to the correct `.db` file 3. **Press F5** to force a full reload of your Supervertaler termbases from disk (note: F5 does not reload MultiTerm termbases) 4. **Reload the database** –click the **gear icon** in the TermLens panel to open settings, then close the dialogue. This forces a reload of the termbase data 5. **Check language pair** –the termbase source and target languages must match the current Trados project languages. Either direction works (the matcher handles inverted-direction termbases automatically), but the language pair itself must match. 6. **Check for reversed entries** –if a single specific term you know exists is silently not matching while other terms in the same segment do, the entry may be stored in the wrong direction in the database (e.g. Dutch text in the English column). This typically affects entries created or edited under v4.19.24 or earlier in projects whose direction was the inverse of the termbase’s. Open the **Termbase Editor** (double-click the termbase in TermLens Settings), find the term, check whether the source and target columns contain text in the expected languages, and use **Reverse source/target** to fix it. See [Termbase Management](/trados/termbase-management/) for details. *** ## MultiTerm terms not appearing **Symptoms:** Green chips from your MultiTerm termbases (`.sdltb` files) are not showing in TermLens, even though the termbases are attached to your Trados project. **Solutions:** 1. **Check your Trados project** –verify that MultiTerm termbases are attached via **Project Settings > Language Pairs > Termbases** 2. **Check the Read toggle** –open Supervertaler Settings (gear icon) and make sure the MultiTerm termbase’s Read checkbox is enabled 3. **Check languages** –the termbase’s source and target languages must match the current project’s language pair 4. **Navigate to another segment and back** to trigger a MultiTerm auto-refresh (F5 does not reload MultiTerm termbases – only segment navigation does) See [MultiTerm Support](/trados/multiterm-support/) for full details. *** ## AI features not working **Symptoms:** Batch Translate produces no output, or single-segment translation returns an error. **Solutions:** 1. **Verify the API key** –open [AI Settings](/trados/settings/ai-settings/) and confirm the key is entered correctly with no extra spaces 2. **Check provider endpoint** –ensure the provider’s API endpoint is reachable from your network (no firewall or proxy blocking it) 3. **Ollama users** –make sure the Ollama service is running locally: ```bash ollama serve ``` Then verify the endpoint in AI Settings (default: `http://localhost:11434`) 4. **Custom provider** –double-check the endpoint URL and model name in the Custom OpenAI-compatible settings 5. **Check your API credits** –some providers return errors when your account balance is zero *** ## Database errors on Mac (Parallels) **Symptoms:** Database locked errors, “cannot open database”, or corrupt termbase data when running Trados Studio inside Parallels Desktop on a Mac. **Cause:** Your Supervertaler data folder is on a Mac-side shared path (e.g., `\\Mac\Home\Supervertaler`). Parallels mounts Mac folders as virtual network shares, and SQLite databases do not work reliably on network filesystems – WAL mode (used by Supervertaler termbases) requires a local filesystem for correct locking. **Solution:** 1. Move your data folder to the Windows side (e.g., `C:\Users\\Supervertaler`) 2. Copy your `.db` termbase files from the Mac-side location into the new Windows-side folder 3. Update the data folder path in Supervertaler settings, or delete `%AppData%\Supervertaler\config.json` and restart Trados to trigger the first-run setup again *** ## Performance issues **Symptoms:** The editor feels sluggish, or TermLens takes a long time to display matches. **Solutions:** * **Large termbases** (50,000+ terms) may take a moment to index when the database is first loaded on startup. This is a one-time cost per session * **Close and reopen the editor** if the plugin feels unresponsive after a long session * **Disable unused termbases** –uncheck **Read** for termbases you do not need for the current project to reduce the matching workload * **Reduce batch size** in [AI Settings](/trados/settings/ai-settings/) if Batch Translate is slow or timing out *** ## Still having issues? 1. Ask a question in [GitHub Discussions](https://github.com/orgs/Supervertaler/discussions) – the community hub for both Supervertaler Workbench and Supervertaler for Trados 2. Check the [GitHub Issues](https://github.com/Supervertaler/Supervertaler-for-Trados/issues) for known bugs, feature requests, and workarounds 3. Open a new issue to report a bug or request a feature, including: * Your Trados Studio version * The Supervertaler plugin version * Steps to reproduce the problem * Any error messages or screenshots See [Support & Community](/trados/support/) for all the ways to get help. *** ## See Also * [Support & Community](/trados/support/) * [MultiTerm Support](/trados/multiterm-support/) * [TermLens Settings](/trados/settings/termlens/) * [AI Settings](/trados/settings/ai-settings/) * [Termbase Management](/trados/termbase-management/) * [Data Folder](/trados/data-folder/) # Token Usage & Costs Supervertaler keeps a **persistent log of the AI tokens and cost** of every operation, and a built-in **Usage & Costs report** to total and export it. This is the place to answer questions like *“how much did this project cost me?”*, *“how many tokens did we use this month?”*, or *“what should I bill this client for AI?”* – and it works for every provider, including custom and self-hosted models. It complements the **[Reports](/trados/reports/)** tab (which shows each call live, as you work) and the **[AI Cost Guide](/trados/ai-cost-guide/)** (which explains how costs work). The usage log is the durable, after-the-fact record. *Added in v4.20.56.* ### The usage log file Every AI call appends one line to a monthly file in your [Supervertaler data folder](/trados/data-folder/): ```plaintext …\Supervertaler\trados\usage\usage-2026-06.jsonl ``` The file is **JSONL** (one JSON object per line), so you can open it directly in Excel, parse it with a script, or load it into a notebook. A single line looks like this: ```json {"ts":"2026-06-18T16:07:03Z","product":"trados","task":"BatchTranslate", "provider":"claude","model":"claude-sonnet-4-6","project":"Example project (patent, en-nl)", "file":"US8312383.docx.sdlxliff","client":"","src_lang":"English (United States)", "tgt_lang":"Dutch (Belgium)","in_regular":654,"in_cache_read":0,"in_cache_write":27843, "out":808,"source":"actual","cost_usd":0.11849325,"cost_known":true,"duration_s":24.9,"ok":true} ``` A few things worth knowing: * **Every flow is covered** – Translate, Batch Translate, Quick Launcher, AutoPrompt, Proofread and Chat. A batch run is recorded as **one** line (the whole job), not one line per segment. * **`source`** is `actual` when the figures are the real token counts reported by the provider’s API, or `estimated` when they fall back to the chars/4 heuristic (see [Estimates vs actual cost](/trados/ai-cost-guide/#estimates-vs-actual-cost)). Cache reads/writes are broken out (`in_cache_read` / `in_cache_write`). * **`cost_known`** is `false` when the model isn’t in the price list – the **tokens are still logged**, the cost just shows as unknown until you add a rate (see [Custom and self-hosted models](#custom-and-self-hosted-models)). * It’s **on by default**. Turn it off any time in **Settings → AI Settings → “Keep a persistent token-usage log”**. ### The Usage & Costs report Open **Settings → AI Settings → “Usage & Costs report…”**. The window totals your logged usage and lets you slice it: * **Range** – This month, Last 3 months, This year, or All time. * **Group by** – **Project**, **Client**, **Model**, **Provider**, **Task** (Translate / Batch / Quick Launcher / …), **Day** or **Month**. Each row shows the number of calls, input and output tokens, total tokens, cost, and a **% actual** column – the share of that group backed by provider-reported figures rather than estimates. The footer shows the **range total** and your **month-to-date spend** (against your budget, if set). ### Exporting The report’s **Export CSV…** and **Export Excel…** buttons write the **detailed ledger** (one row per call, every column) for the selected range – ready for invoicing or analysis in any spreadsheet. CSV is written as UTF-8 (with a BOM, so Excel detects it correctly); Excel export produces a native `.xlsx`. Because both Supervertaler products write the **same columns**, an LSP can concatenate the CSV/JSONL from several translators – and from both Trados and Workbench – into one analysis. ### Monthly budget Set a soft monthly limit in **Settings → AI Settings → “Monthly budget (USD)”** (cents are allowed, e.g. `25.50`; `0` disables it). It is **advisory and never blocks**: once this month’s logged spend reaches the budget, starting a **Batch Translate** shows a *“Monthly budget reached – start anyway?”* prompt, so a large run can’t slip past unnoticed. Your month-to-date spend versus the budget is also shown in the Usage & Costs report. ### Custom and self-hosted models Costs are computed from a single price list, **`pricing.json`**, shared with Supervertaler Workbench. The bundled copy covers the built-in models. To price a **custom or self-hosted model** (or to override any rate for **both** Supervertaler products at once): 1. Copy the bundled `pricing.json` to `…\Supervertaler\pricing.json` (the shared data root), or create it there. 2. Add an entry under `models` keyed by the **exact model id** you use, with the input/output price per 1,000,000 tokens: ```json { "models": { "my-university-llama": { "input": 0.0, "output": 0.0 } } } ``` 3. Restart Supervertaler. Its cost now appears in the log and report; until then, its **tokens are still logged** with the cost marked unknown. Local models (Ollama) are priced at `0` – their token counts are still recorded, which is useful for capacity planning. ### See also * [AI Cost Guide](/trados/ai-cost-guide/) – how AI costs work, estimates vs. actual, provider dashboards * [Reports](/trados/reports/) – live, per-call token counts and cost as you work * [AI Settings](/trados/settings/ai-settings/) – where the toggle, budget and report button live * [Batch Translate](/trados/batch-translate/) – the main driver of token usage * [Data folder](/trados/data-folder/) – where the usage log and project files live # Voice Commands Control Trados Studio hands-free with spoken commands: confirm segments, navigate, insert TermLens matches, apply translation results, add terms and more – without touching your keyboard. Designed to pair with dictation tools such as Wispr Flow or Dragon: they type your translation, Supervertaler handles the commands. ### Starting and stopping Two ways to toggle voice commands: * Click the **🎤 microphone button** in the TermLens panel header (next to the ↻ refresh button) * Press **Ctrl+Alt+D** (also available in the editor right-click menu)  The 🎤 button in the TermLens header – green while listening The microphone button shows the state at a glance: | Colour | Meaning | | ---------- | -------------------------------------------------------- | | **Grey** | Off – click to start | | **Orange** | Starting (or downloading the voice runtime on first use) | | **Green** | Listening | Each command you speak flashes briefly in the TermLens status label (e.g. `🎤 "confirm"`), so you always know what was heard. If the TermLens panel isn’t open, a small floating status strip appears instead (bottom-right). You can drag it anywhere – the position is remembered. ### Default commands Everything works out of the box – no configuration needed. Most commands also respond to an alias, so you can use whichever phrasing comes naturally: | Say | Or | Action | | -------------------------- | ---------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- | | ”select …" | "choose …” | Select those words in the target – see [Dictation](/trados/voice-commands/dictation/) | | ”delete that" | "delete this”, “remove that” | Delete whatever is selected in the target | | ”undo that" | "scratch that”, “undo” | Undo the last change (Ctrl+Z) | | “dictate" | "stop now” | Hand over to an external dictation tool and take it back (**off by default** – see [Dictation](/trados/voice-commands/dictation/)) | | “confirm" | "confirm segment” | Confirm segment and move to next unconfirmed | | ”next segment" | "go down” | Move to the next segment (without confirming) | | “previous segment" | "go up” | Move to the previous segment | | ”go to the top" | "go to top” | Jump to the first segment (Ctrl+Home) | | “go to the bottom" | "go to bottom” | Jump to the last segment (Ctrl+End) | | “copy source" | "copy from source” | Copy source to target | | ”clear target” | | Clear the target segment | | ”term one” … “term nine” | | Insert TermLens match 1–9 (with [capitalisation adaptation](/trados/termlens/#automatic-capitalisation)) | | “match one” … “match nine” | | Apply Translation Results match 1–9 (Ctrl+1–9) | | “term picker" | "pick term” | Open [TermPicker](/trados/termlens/termpicker/) | | ”term popup" | "show terms” | Open the [TermLens popup](/trados/termlens/termlens-popup/) | | ”add term" | "new term” | Quick-add the selection to your write termbases (Alt+Down) | | “add project term" | "project term” | Quick-add the selection to the project termbase (Alt+Up) | | “translate" | "translate segment” | AI-translate the active segment | | ”concordance" | "search memory” | Concordance search on the selection (F3) | | “zoom in" | "bigger font” | Increase the editor font size (see setup below) | | “zoom out" | "smaller font” | Decrease the editor font size (see setup below) | | “escape" | "close window” | Close the focused popup or dialog | | ”stop listening" | "voice off” | Turn voice commands off | ### One-time setup for “zoom in” / “zoom out” Trados Studio’s font-size actions ship **without a default keyboard shortcut**, so these two commands need a one-time binding: 1. Go to **File > Options > Keyboard Shortcuts > Editor** 2. Scroll down to the actions named simply **Increase** and **Decrease** (note: the Keyboard Shortcuts page has no search box – you have to scroll) 3. Set **Increase** to `Ctrl+Alt+PgUp` and **Decrease** to `Ctrl+Alt+PgDn` 4. Click **OK** From then on, “zoom in” and “zoom out” control the editor font size hands-free. (Make sure **Adapt font sizes** is enabled under File > Options > Editor > Font Adaptation.) ### Safety and privacy * **Fully offline** – recognition runs locally on your machine (Vosk engine); no audio is ever sent anywhere. * **Grammar-constrained** – the recogniser listens *only* for your command phrases, which is what makes commands fast and reliable. Normal speech and dictation are ignored. * **Foreground guard** – commands only execute while Trados Studio is the active window. Speaking in another app can’t trigger anything (“stop listening” is the one exception – it always works). ### Customising commands Right-click the 🎤 button (or click ⚙ on the floating strip) to open the **Voice command settings** dialog (also reachable via the **?** in its title bar and **F1** for this help page):  Voice command settings – every phrase, alias and action is editable * Enable/disable individual commands * Edit spoken phrases and add aliases * Add your own commands, mapped to either: * a **keystroke** chord sent to Studio (e.g. `ctrl+enter`, `alt+up`, `f3`) – any Studio or Supervertaler shortcut works * an **internal** plugin action: `insert_term_1`…`insert_term_9`, `term_picker`, `termlens_popup`, `navigate_next`, `navigate_previous`, `stop_listening`, `select_phrase`, `delete_selection`, `dictate_toggle` A phrase containing `{phrase}` – as in `select {phrase}` – takes the words you say after it as its argument, rather than matching exactly. Only `select_phrase` uses this. #### Choosing words for a command The recogniser works from a closed vocabulary: your command phrases, plus the words of the segment you are in. It has no option to return nothing, so it always picks the best match from that list – which means **every word you add competes for that sound in every segment**, including against the words of your own translation. The number of commands barely matters: a long list of distinctive phrases costs nothing. What costs you is a single command built from a short, everyday word. * **Prefer distinctive words.** “insert tracked change” is free. A command called “to” or “for” is expensive, because it competes with those words wherever they appear in your text. * **Untick what you do not use.** Disabled commands are removed from the vocabulary entirely, so turning off the “term …” or “match …” numbers you never reach makes the rest more reliable. * **Watch for one word that will not select.** If [selecting](/trados/voice-commands/dictation/) a particular word keeps failing, the cause is usually a command phrase that sounds like it. Homophones are the trap, not spelling. The built-in “term eight” and “match eight” commands put *eight* into the vocabulary of every segment, and *eight* sounds exactly like the article *a* – so for a while, “select a further” could not be made to work at all. Supervertaler now resolves the number words that have common homophones (*a/eight*, *to/two*, *for/four*, *one/won*) back to the word your segment actually contains, but a custom command can reintroduce the problem with a different word. Commands are stored in `trados/settings/voice_commands.json` in your Supervertaler data folder, in the same format as Supervertaler Workbench’s voice commands – so you can exchange command sets between the two products. Default commands added in plugin updates are **merged into your saved set automatically** – your customisations are never touched. Because of this, if you want to get rid of a default command, **untick it rather than delete it** (a deleted phrase would come back if a later update re-ships it). **Restore defaults** replaces everything with the built-in set, discarding your customisations. ### Troubleshooting * **“Voice commands could not start”** – check that a microphone is available in Windows sound settings, and that the first-run download completed (an interrupted download can be retried by simply starting voice commands again). * **A command isn’t recognised** – speak the phrase on its own, at normal pace. If a phrase never triggers, give it a more distinctive alias in Voice command settings. * **Corrupt model** – delete the `trados/voice/models` folder in your Supervertaler data folder; the next activation re-downloads it. ### See Also * [Dictation](/trados/voice-commands/dictation/) * [Keyboard Shortcuts](/trados/keyboard-shortcuts/) * [TermLens](/trados/termlens/) * [TermPicker](/trados/termlens/termpicker/) # Dictation Voice commands drive Trados Studio. A dictation tool writes your translation. This page is about the seam between the two – selecting words you have just dictated, replacing them, and handing the microphone back and forth without touching the keyboard. Everything here works with any dictation tool. [Wispr Flow](https://wisprflow.ai/) is the one the feature was built and tested against, so it is used for the worked example, but Dragon, Windows Voice Access and the rest follow the same three setup steps. ### Why two tools at all The two jobs need opposite things from a recogniser. **Commands** need a closed vocabulary. Supervertaler’s recogniser is given a short list of phrases and hears nothing else, which is what makes “confirm” fire instantly and reliably, and what stops your prose from triggering anything. It runs offline, on your machine. **Prose** needs the opposite: an open vocabulary, punctuation, capitalisation, and – for most of us – a second language. That is a different kind of engine, and dictation tools already do it well. So Supervertaler does not try to transcribe your translation. It selects, deletes, undoes, and gets out of the way. ### Editing what you just dictated Three commands, all on by default: | Say | Or | Action | | ----------------- | ---------------------------- | ------------------------------------------------------------------------- | | ”select …" | "choose …” | Select those words in the target segment | | ”select source …" | "source …” | Select those words in the **source** segment (off by default – see below) | | “delete that" | "delete this”, “remove that” | Delete whatever is selected | | ”undo that" | "scratch that”, “undo” | Undo the last change (Ctrl+Z) | “select” is followed by the words you want, not by a fixed phrase: **“select the duty cycle”**, **“select sealing ring”**. While a segment is open, every word of its target is added to the recogniser’s vocabulary, so it can hear the words that are actually in front of you. A few things worth knowing, because they explain what you will see: * **Dropped words are tolerated.** Unstressed function words often do not survive recognition – “comprises at most” comes back as “comprises most”. The selection widens to the segment’s own text, so you still get *comprises at most*. * **Whole words only.** Saying “select the” selects the standalone *the*, never the three letters inside *further*. * **Say it again for the next one.** Where a phrase occurs more than once, the first is selected and the status strip says **2 of 4 – say again for the next**. Repeating the same phrase steps to the next occurrence, and wraps round at the end. Naming more words works too. * **It only searches the target.** Source text, other segments and the termbase are not candidates. If a phrase cannot be selected, the status strip says why rather than doing nothing – `no "confirm" in this segment`, or `"the" is inside another word – say more words`. A selection in a place you did not name would be worse than none, because “delete that” would act on it. ### Selecting in the source `select source …` does the same thing in the **source** segment – useful for looking a term up, running a concordance, or adding a source/target pair to a termbase without touching the keyboard: **“select source cockpitdisplay”** → **“select cockpit display”** → **“add term”** It is **off by default**, because the source is usually in another language and needs a voice model for it. Tick **`select source {phrase}`** in Voice command settings; the first time you use it, the model for your project’s source language downloads in the background (\~40 MB, once) and the status strip tells you when it is ready. #### Long compounds In Dutch, German and other compounding languages, the word you want is often one the recogniser has never seen: languages like these build words on demand, so no dictionary contains them all. `beschermingsperiode` and `infraroodtouchscreens` are not in any Vosk Dutch model, large or small – this is a property of the language, not a limitation to be fixed with a bigger download. Supervertaler works around it by offering the recogniser the *parts* of every long word in the segment, and accepting any part as naming the whole word. So **“select source bescherming”** selects `beschermingsperiode`, and saying the compound naturally works too, because whichever part is heard is enough. A word with no recognisable part at all – a foreign loanword, typically – still cannot be selected. Name a neighbouring word instead. ### Handing over to a dictation tool The **“dictate”** command starts your dictation tool, stands aside while you talk, and stops it when you say “dictate” again. It ships **switched off**, because it drives a tool most installations do not have – switch it on in Voice command settings once you have done the setup below. While dictation is running, Supervertaler ignores every command except the way back out (and “stop listening”, which always works). This is the part a general-purpose macro tool cannot do: because it was *your command* that started the dictation, Supervertaler knows you are in it, and a translation containing the word “confirm” cannot fire a command into your document mid-sentence. #### Setup, with Wispr Flow as the example **1. Give the dictation tool a hands-free shortcut.** The “dictate” command is shipped expecting **Ctrl+Win+Space**, which is one of Wispr Flow’s own hands-free defaults, so there is usually nothing to change. Push-to-talk will not do – it needs a key held down, and the point here is not to touch the keyboard. **2. Teach it to write a marker for your stop phrase.** When you say “dictate” to stop, the dictation tool is still listening, so the word lands in your text. Rather than trying to guess and delete it, have the tool write a fixed marker instead: * In Wispr Flow, open **Dictionary** and add an entry mapping **dictate** to **ZZEND**. Supervertaler waits for `ZZEND` to appear and removes it, along with the space before it. A marker is used rather than an empty replacement for two reasons: most tools will not map a phrase to nothing, and a marker is far more reliable – spoken, your stop word arrives formatted, capitalised and punctuated (`. Dictate.`), and every one of those variants collapses into one fixed string you can search for. **3. Switch the command on.** Right-click the 🎤 button → **Voice command settings** → tick **dictate**. If your tool uses a different shortcut, or a different marker, edit the command’s action rather than any settings screen: it reads `dictate_toggle:ctrl+win+space:ZZEND` – trigger first, marker second. `dictate_toggle:middleclick` is accepted for a tool that listens for a middle click. ### Putting it together A correction, hands-free, start to finish: 1. **“select the duty cycle”** – the words highlight in the target 2. **“dictate”** – your dictation tool starts listening 3. *“the duty factor”* – it types over the selection 4. **“dictate”** – it stops, the marker is cleaned up 5. **“confirm”** – segment confirmed, on to the next If step 3 comes out wrong, **“undo that”** puts it back. ### Limitations * **The stop phrase must be distinct from your prose.** It is a word your dictation tool is listening for, so choosing a word you dictate often will bite you. * **A word buried in an earlier word, at the very end of a segment, cannot be selected.** There is nothing after it to tell the two apart. Say two words instead. * **Selection follows the active segment.** Move to another segment and the vocabulary changes with it. * **A word the recogniser has never seen cannot be selected**, and nor can a compound none of whose parts it knows. Name a word next to it instead. * **The status strip is the feedback channel.** Keep the TermLens panel open, or use the floating strip, so you can see what was heard and what happened. ### See Also * [Voice Commands](/trados/voice-commands/) * [Keyboard Shortcuts](/trados/keyboard-shortcuts/) * [TermLens](/trados/termlens/)