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 Self-organising, AI-maintained translation knowledge base. Stores client profiles, terminology decisions, domain conventions, and style preferences as interlinked Markdown files. The AI consults the active memory bank automatically when translating. Keep separate banks per client or domain and switch between them from the toolbar dropdown. Quick-add terms and corrections 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 as an inbox note in the active memory bank so useful answers are not lost. Run [Process Inbox](/trados/ai-assistant/super-memory/process-inbox/) afterwards to compile it into the knowledge base. | If you select text within a bubble before right-clicking, **Copy** and **Apply to target** operate on the selection only. ## Features | Feature | Description | | ---------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ | | [**Context Awareness**](/trados/ai-assistant/context-awareness/) | Automatic project, segment, terminology, TM, and document context in every request | | [**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 that lets Supervertaler Workbench’s floating Sidekick Chat read your active Trados project context | ## 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. # Context Awareness The Supervertaler Assistant is deeply integrated with your Trados project. Every time you send a chat message, translate a batch of segments, or ask AutoPrompt to draft a prompt, the assistant assembles a fresh snapshot of your current work and hands it to the AI. This snapshot is the **context** – everything the AI sees before it produces a reply. This page is the single place that lists every context source. Each section is a brief overview with a link to the feature’s canonical page for more depth. If you have ever wondered *“what exactly does the AI know when I ask it something?”*, the answer is this page. ## The context sources Supervertaler draws context from eight sources. They are all independent, they can all be toggled individually, and most of them are on by default. ### 1. Project and file information The assistant knows which project and file you are working in, the language pair (e.g. Dutch → English), and your current position in the document (e.g. “Segment 42 of 318”). This is always included – there are no user-facing toggles for it. ### 2. Full document content When enabled, all source segments in the current document are included in the AI prompt. This lets the assistant analyse the document as a whole and determine its type – legal, medical, technical, marketing, financial, scientific – then use that assessment to inform its advice on terminology, style, and translation choices. For very large documents, the content is automatically truncated to the configured maximum (default: 500 segments). The truncation preserves the first 80 % and the last 20 % of the document so the AI still sees both the beginning and the end. **Toggle:** AI Settings → *Include full document content*. ### 3. Current segment The source text you are translating and any target translation you have already entered. Always included – this is the minimum context needed for most AI operations. ### 4. Surrounding segments Two segments before and two segments after your current position, with their translations where available. This gives the AI local context for cohesion and consistency – it can see how a pronoun was resolved in the previous sentence, or whether the current clause is continuing a thought from the segment above. Always included – the window size is fixed. ### 5. Translation memory matches TM fuzzy matches for the current segment are included, showing the match percentage, source text, and target text. This gives the AI reference material from your previous translations – it can see how you or your team rendered a similar phrase last time and stay consistent with that. **Toggle:** AI Settings → *Include TM matches*. ### 6. Termbase terms Matched terms from your active termbases are included with their approved translations and synonyms. Optionally, term definitions, domains, and usage notes are also included, giving the AI deeper understanding of your terminology requirements. Terms marked as non-translatable or forbidden are flagged so the AI can respect those constraints. Both Supervertaler termbases and MultiTerm .sdltb termbases attached to the Trados project contribute. See [TermLens](/trados/termlens/) and [MultiTerm Support](/trados/multiterm-support/) for how those termbases are loaded. **Toggles:** AI Settings → *Include termbase terms* / *Include term metadata* / per-termbase contribution list. ### 7. SuperMemory context [**SuperMemory**](/trados/ai-assistant/super-memory/) is Supervertaler’s self-organising translation knowledge base system. If a memory bank is active, the assistant loads the most relevant articles from it before every AI call: * the **client profile** matching the current Trados project name, from `01_CLIENTS/` * the **domain article** matching the document type the AI just detected, from `03_DOMAINS/` * the most relevant **style guide** from `04_STYLE/`, preferring client-specific guides over general ones * matching **terminology articles** from `02_TERMINOLOGY/`, which include not just approved translations but also rejected alternatives and the reasoning behind each decision Unlike a termbase – which gives the AI flat pairs of source and target terms – SuperMemory gives it the **reasoning** behind those pairs: the decisions, the caveats, and the client-specific overrides. The two are complementary, not competitive. Only articles from the **active** memory bank are loaded. If you keep separate banks per client or domain, switch to the relevant one from the Memory Bank dropdown in the toolbar before translating. See [SuperMemory → AI Integration](/trados/ai-assistant/super-memory/ai-integration/) for the full loading algorithm and token budget. **Toggles:** AI Settings → *Include memory bank context* / *Use memory bank in AutoPrompt*. ### 8. Attached files Files you attach to the chat panel – images (paste, drag-drop, or browse), and documents (DOCX, PDF, PPTX, XLSX, CSV, TMX, SDLXLIFF, TBX, TXT, Markdown, HTML, and more) – are added to the context for that turn. Images are sent through each provider’s vision API; documents are text-extracted and appended as prompt context. Attachments only apply to the turn you attached them on – they do not persist across messages. See [File Attachments](/trados/ai-assistant/file-attachments/) for details. ## Composing the context All eight sources can be combined freely. For most projects, the default composition – project info, current segment, surrounding segments, document content, TM matches, termbase terms, and memory bank context all enabled – is a strong baseline and the one we recommend starting from. That said, more context is not automatically better. The AI’s context window is finite, and large projects with rich termbases and a mature memory bank can easily push the 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 introduce noise rather than signal; * including **full document content** for a very long document may leave too little room for memory bank articles 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. Caution We have not yet published composition presets (e.g. “Mature client – memory bank only”, “Unfamiliar domain – TM + termbase”). Until we do, the sensible approach is to leave everything enabled by default and experiment on a per-project basis. If you find a configuration that works particularly well for your workflow, drop a note in [GitHub Discussions](https://github.com/orgs/Supervertaler/discussions). ## Controlling the context ## See Also * [Supervertaler](/trados/ai-assistant/) – Overview * [AI Settings](/trados/settings/ai-settings/) – Configure context options * [SuperMemory](/trados/ai-assistant/super-memory/) – Supervertaler’s self-organising translation knowledge base system * [SuperMemory → AI Integration](/trados/ai-assistant/super-memory/ai-integration/) – The loading algorithm and token budget for SuperMemory context * [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 # 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 Awareness](/trados/ai-assistant/context-awareness/) — 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 Awareness](/trados/ai-assistant/context-awareness/)** – exactly what Supervertaler puts in front of the AI (current segment, surrounding segments, terminology, TM matches, memory bank) 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 **AI context (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 Awareness](/trados/ai-assistant/context-awareness/) — 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 Supervertaler’s self-organising translation knowledge base system – a [Karpathy-inspired](https://venturebeat.com/data/karpathy-shares-llm-knowledge-base-architecture-that-bypasses-rag-with-an) feature that captures the reasoning behind your translation decisions and makes it available to the AI on every translation. Where a translation memory gives the AI previous wordings and a termbase gives it approved term pairs, SuperMemory gives it the *why*: client preferences, rejected alternatives, domain conventions, style rules, and the accumulated institutional knowledge for each piece of work. Knowledge inside SuperMemory is organised into one or more **memory banks** – self-contained folders that each act as an Obsidian-compatible vault. You can keep a single default bank, or several banks side by side (one per client, one per domain, one per language pair) and switch between them in one click from the Supervertaler Assistant toolbar. This page covers both SuperMemory as a system and how to work with the memory banks inside it. SuperMemory is one of several [context sources](/trados/ai-assistant/context-awareness/) the assistant consults when it translates a segment, drafts a prompt, or answers a chat message. It sits alongside termbases, translation memories, document content, and segment metadata – you can enable any combination of the five, and the AI draws from whichever are active in AI Settings. Each memory bank is stored as interlinked Markdown files on disk – human-readable, portable, and future-proof. You can open and edit a bank in any text editor, version-control it with Git, and sync it between machines with Dropbox or OneDrive. [Obsidian](https://obsidian.md/) is optional but recommended: it gives you a visual knowledge graph, backlink navigation, and the Web Clipper browser extension for clipping web content directly into your bank. See [Obsidian Setup](/trados/ai-assistant/super-memory/obsidian-setup/) for installation instructions.  A memory bank knowledge graph showing interconnected clients, terminology, and domain knowledge ## How knowledge is organised Every memory bank has the same seven-folder skeleton. The skeleton is created automatically when you make a new bank, and it is shared byte-for-byte with the Python Supervertaler – so a bank created in Trados works unchanged in the standalone app and vice versa. | Folder | Contents | | ---------------- | ----------------------------------------------------------------------------------------------------- | | `00_INBOX` | Raw material – drop zone for unprocessed briefs, feedback notes, termbases, reference articles | | `01_CLIENTS` | Client profiles: language preferences, style rules, terminology decisions, project history | | `02_TERMINOLOGY` | Term articles with approved translations, rejected alternatives, and the reasoning behind each choice | | `03_DOMAINS` | Domain-specific conventions and common pitfalls (legal, medical, technical, marketing, financial) | | `04_STYLE` | Style guides, formatting rules, register notes, localisation conventions | | `05_INDICES` | Auto-generated indexes and maps of content | | `06_TEMPLATES` | Reusable templates for new articles | The assistant loads content from `01_CLIENTS`, `02_TERMINOLOGY`, `03_DOMAINS`, and `04_STYLE` as context before each AI call. `00_INBOX`, `05_INDICES`, and `06_TEMPLATES` are workflow folders – they do not feed the AI directly, they support the processing pipeline. See [AI Integration](/trados/ai-assistant/super-memory/ai-integration/) for the full loading algorithm. ## Creating and switching banks ### Where banks live on disk All of your memory banks live under a single parent folder – the **memory banks folder** – which defaults to: ```plaintext C:\Users\{you}\Supervertaler\memory-banks\ ``` Each bank is a subfolder with the seven-folder skeleton shown above: ```plaintext memory-banks\ ├── default\ │ ├── 00_INBOX\ │ ├── 01_CLIENTS\ │ └── … ├── acme-legal\ │ ├── 00_INBOX\ │ └── … └── pharma\ └── … ``` A fresh install ships with one empty bank named `default`. You can keep that as your only bank, rename it (see below), or add others alongside it. ### Switching banks The **Memory Bank** dropdown in the Supervertaler Assistant toolbar lists every bank it finds under the memory banks folder. The one you pick is the **active bank** – the assistant reads from it until you choose another. Switching is immediate: the next chat turn, the next batch translation, and the next Process Inbox run all use the new bank. No restart needed, and your chat history is preserved across the switch. The active bank persists across Trados sessions. If you close Trados with `acme-legal` selected, it will still be `acme-legal` when you reopen. ### Creating a new bank To create a new bank without leaving the chat panel: 1. Click the **Memory Bank** dropdown in the Supervertaler Assistant toolbar. 2. Scroll to the bottom of the list and choose **+ New memory bank…** 3. A small dialog appears asking for a short name. Valid names are lowercase letters, digits, hyphens, or underscores – for example, `legal`, `medical`, `acme-corp`, `eu_procurement`. As you type, the dialog shows a live preview of the folder name that will be created. 4. Click **Create**. The new bank is created on disk with the full seven-folder skeleton, the dropdown refreshes to show it, and the assistant switches to it immediately. A confirmation banner appears in the chat summarising what was created. ### Renaming and deleting banks Renaming and deleting banks from inside the plugin is not yet available. Until those land, you can rename or delete a bank folder directly under `memory-banks\` using File Explorer, with Trados closed. Be sure to update `AiSettings.ActiveMemoryBankName` in your settings file if you rename the active bank, or simply switch to another bank from the toolbar dropdown the next time you open Trados. ## Why run several banks A single `default` bank is enough if you work with one client or one domain. But most working translators will benefit from splitting their knowledge across several banks – one per major client, or one per domain, or one per language pair – because: * **Context stays sharp.** The AI’s context window is finite. A focused bank for a single client fits entirely in the prompt; a monolithic bank covering ten clients either exceeds the budget or has to be aggressively pruned before loading, losing detail. * **Switching is instant.** When you move from translating a pharma clinical trial to a tech product manual, you want the AI to forget the pharma terminology immediately. Switching banks does that in one click. * **Confidentiality is structural.** A bank for Client A physically cannot leak into a translation for Client B because the folders are separate on disk. No accidental cross-contamination. * **Backups and syncing are per-client.** You can version-control, archive, or share a single client bank without exposing your other clients’ data. Typical layouts: * **One bank per major client** – `acme-legal`, `novartis`, `eu-commission`, plus a small `default` for one-off work. * **One bank per domain** – `legal`, `medical`, `technical`, `marketing`. * **One bank per language pair** – `nl-en`, `de-en`, `fr-en` if your domains are similar across clients but the style and terminology vary by direction. ## Sharing banks with the Python Supervertaler Memory banks are stored in the **shared Supervertaler data folder** – the same folder the Python Supervertaler uses – so banks created on either side are immediately visible to the other. The folder layout, skeleton, and naming rules are identical byte-for-byte. You can create a bank in the Python assistant, drop files into its inbox from the web clipper, and then switch to it from the Trados plugin; both products will see the same articles. The shared folder also means you can keep your memory banks in a cloud-synced location (OneDrive, Dropbox, iCloud) and have the same banks available on any machine where either product is installed. ## Working with a memory bank Once a bank exists, you fill it with knowledge in one of several ways: 1. **Drop Markdown notes into `00_INBOX`** – client briefs, termbases, feedback notes, style guides, reference articles you have written down as `.md` files. These are compiled by Process Inbox. 2. **Use** [**Distill**](/trados/ai-assistant/super-memory/distill/) for everything that is **not** plain Markdown – TMX translation memories, DOCX style guides, PDF reference documents, XLSX/CSV termbases, MultiTerm termbases. Distill reads each file and writes draft Markdown articles into `00_INBOX/`, ready for Process Inbox to compile. 3. **Use** [**Quick Add**](/trados/ai-assistant/super-memory/quick-add/) (Ctrl+Alt+M) to capture a terminology decision or correction while translating. Quick Add appends a short note to the inbox so you can keep working without context-switching. 4. **Run** [**Process Inbox**](/trados/ai-assistant/super-memory/process-inbox/) periodically. The AI reads every Markdown file in `00_INBOX` and files it into `01_CLIENTS`, `02_TERMINOLOGY`, `03_DOMAINS`, or `04_STYLE` as structured articles, interlinked with backlinks. 5. **Run** [**Health Check**](/trados/ai-assistant/super-memory/health-check/) when the bank starts to feel stale. It scans for conflicting terminology, broken links, stale content, and missing cross-references – and heals what it can. The result is a knowledge graph that grows with your work and that the AI consults before every translation. ### Templates and the heal-on-activation prompt Process Inbox and Health Check are driven by AI prompts that live inside each bank under `06_TEMPLATES/` (`compile.md` and `lint.md` respectively). The plugin ships these template files as built-in defaults, and `+ New memory bank…` writes them automatically into every newly created bank. If you activate an older bank that is missing one of these template files – for example a bank you created before template bundling shipped, or one where you deleted a template by accident – the plugin shows a one-time *“Missing memory bank templates”* dialog offering to restore the missing files from the built-in defaults. Click **Yes** and the bank is fixed in place; click **No** and the plugin leaves the bank alone (you can switch away and back to see the prompt again). Existing template files are never overwritten – only missing ones are written – so your per-bank edits are safe. ## Features | Feature | Description | | ----------------------------------------------------------------------- | -------------------------------------------------------------------- | | [**Quick Add**](/trados/ai-assistant/super-memory/quick-add/) | Capture terms and corrections while translating (Ctrl+Alt+M) | | [**Process Inbox**](/trados/ai-assistant/super-memory/process-inbox/) | Organise raw material into structured KB articles | | [**Health Check**](/trados/ai-assistant/super-memory/health-check/) | Scan and repair the knowledge base | | [**Distill**](/trados/ai-assistant/super-memory/distill/) | Extract knowledge from translation files (TMX, DOCX, PDF, termbases) | | [**Active Prompt**](/trados/ai-assistant/super-memory/active-prompt/) | Per-project prompt that Quick Add appends terminology to | | [**AI Integration**](/trados/ai-assistant/super-memory/ai-integration/) | How the memory bank enhances translations and chat | | [**Obsidian Setup**](/trados/ai-assistant/super-memory/obsidian-setup/) | Installing Obsidian and the Web Clipper | ## Related * [**Context Awareness**](/trados/ai-assistant/context-awareness/) – the full menu of context sources the assistant uses, with memory banks as one section among several. * [**AI Integration**](/trados/ai-assistant/super-memory/ai-integration/) – the loading algorithm, token budget, and article prioritisation when a memory bank is consulted by the AI. * [**AI Settings**](/trados/settings/ai-settings/) – toggles for enabling or disabling memory bank context. ## Learn more The memory bank design is inspired by Andrej Karpathy’s [LLM Knowledge Base](https://venturebeat.com/data/karpathy-shares-llm-knowledge-base-architecture-that-bypasses-rag-with-an) architecture. Templates for the seven-folder skeleton are available on [GitHub](https://github.com/Supervertaler/Supervertaler-SuperMemory) (the repository still uses the project’s original name). # 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 > How SuperMemory is loaded into the AI context – the algorithm, ranking, and token budget This page is the technical deep dive into **how** SuperMemory – Supervertaler’s self-organising translation knowledge base system – loads the active memory bank into the AI context. For the broader picture of all context sources, start with [Context Awareness](/trados/ai-assistant/context-awareness/). For what SuperMemory is and how to create and switch memory banks, start with [SuperMemory](/trados/ai-assistant/super-memory/). When SuperMemory context is enabled in [AI Settings](/trados/settings/ai-settings/), every AI call – chat messages, batch translations, single-segment translations, AutoPrompt runs – triggers a fresh load of the active memory bank before the prompt is sent. The load is deterministic, fast, and scoped to the current project and document. ## What the AI loads Before every AI call, Supervertaler reads the active memory bank and loads the most relevant articles from it: 1. **Client profile.** The assistant matches your Trados project name against client profile filenames in `01_CLIENTS/`. If your project is called “Acme Legal Contract 2026”, it finds the Acme Corporation profile and loads the client’s language preferences, terminology decisions, style rules, and project history. The match is a case-insensitive substring search against the filename and the top-level heading of each article. 2. **Domain article.** The assistant analyses your document to detect the domain (legal, medical, technical, marketing, financial, scientific) and loads the matching article from `03_DOMAINS/` with conventions, common pitfalls, and reference material for that field. 3. **Style guide.** The assistant loads the most relevant style guide from `04_STYLE/`, preferring client-specific guides (e.g. `acme-style.md`) over general ones (e.g. `general-en-gb.md`). 4. **Terminology articles.** The assistant loads term articles from `02_TERMINOLOGY/` that match your client, domain, or language pair. These include not just the approved translations, but also rejected alternatives and the reasoning behind each decision – the kind of context a flat termbase entry does not carry. Only articles from the **active** memory bank are loaded. If you keep separate banks per client or domain, switch to the relevant one from the Memory Bank dropdown in the toolbar before translating. See [SuperMemory → Creating and switching banks](/trados/ai-assistant/super-memory/#creating-and-switching-banks) for the switching workflow. Workflow folders – `00_INBOX`, `05_INDICES`, and `06_TEMPLATES` – are **not** loaded into the AI context. `00_INBOX` is a processing queue, `05_INDICES` holds auto-generated maps, and `06_TEMPLATES` holds templates for new articles. ## Token budget and prioritisation To avoid overloading the AI’s context window, memory bank context is allocated a token budget of approximately **4000 tokens** per AI call. This is a soft ceiling – smaller banks will simply fit; larger ones are trimmed. When the active bank contains more relevant content than fits in the budget, articles are prioritised in this order: 1. **Client profile** – highest priority, loaded first. The client profile is often the single most valuable article in the bank because it sets the stage for everything else. 2. **Domain knowledge** – loaded second, with the strongest match for the detected document type. 3. **Style guide** – loaded third, preferring client-specific over general. 4. **Terminology articles** – loaded last, filling whatever budget remains. Articles matching the client take priority over generic ones. If even the client profile exceeds the budget, Supervertaler logs a warning to the chat history and loads a truncated version rather than silently dropping it. ## How memory banks compare with other context sources A memory bank does not replace your termbases, translation memories, or document context – it **complements** them, adding a layer of reasoning that flat data sources cannot provide. | Context source | What it provides | What the memory bank adds | | ----------------------------------------- | ----------------------------------------- | ----------------------------------------------------------------------------------- | | **Termbases** (Supervertaler + MultiTerm) | Flat term pairs: term A = term B | The *why*: reasoning, rejected alternatives, client-specific overrides | | **Translation memories** | Previous translations for style anchoring | Domain conventions and style rules that transcend any single segment | | **Document content** | Document type detection | Domain-specific pitfalls and formatting conventions the AI would not otherwise know | | **AutoPrompt** | AI-generated translation instructions | Client and domain context for more accurate prompt generation | All four work together. Termbases give the AI the terms; the memory bank tells it *why* those terms were chosen and what to watch out for. A TM gives it previous translations to anchor against; the memory bank tells it which previous translations are from a client with strict style rules and which are from one-off work that can be safely overridden. For a discussion of when stacking all four sources may or may not be optimal, see the **Composing the context** section of [Context Awareness](/trados/ai-assistant/context-awareness/#composing-the-context). ## Memory-aware chat Once memory-bank context is enabled (see below), the chat panel is memory-aware. When you ask the assistant a question about the current segment, it has access to the active memory bank alongside the document context, terminology, and TM matches – so you can ask things like: * “What register should I use for this client?” * “Does this client prefer *whilst* or *while*?” * “Has this term come up before in this client’s projects?” * “What’s the usual translation for *furtherance* in this domain, and why?” …and the answer comes from your actual KB articles, not from generic training data. If the memory bank does not contain the relevant article, the assistant falls back to its general knowledge and says so. ## Enabling and disabling Memory bank context can be toggled on or off in [AI Settings](/trados/settings/ai-settings/): * **Include memory bank in AI context** – enables KB context for translations and chat. * **Use memory bank when generating prompts (AutoPrompt)** – enables KB context when AutoPrompt drafts a new translation prompt. Both are **off by default** – turn on *Include memory bank in AI context* to activate the integration described on this page. Disabling them again does not delete your memory banks – the content stays on disk and can be re-enabled at any time. ## See Also * [Context Awareness](/trados/ai-assistant/context-awareness/) – The full menu of context sources, including memory banks as one section among several * [SuperMemory](/trados/ai-assistant/super-memory/) – What SuperMemory is, what memory banks are, and how to create one * [AI Settings](/trados/settings/ai-settings/) – Toggles for memory bank context * [Supervertaler](/trados/ai-assistant/) – Overview of the chat panel * [Batch Translate](/trados/batch-translate/) – Batch translation with full context # Distill > Extract knowledge from translation files using AI **Distill** extracts knowledge from professional translation files and creates structured knowledge base articles in the active memory bank’s inbox. Instead of manually reading through a 50,000-segment translation memory or a 30-page client style guide, the AI analyses the content and distils it into actionable articles: terminology decisions, style conventions, client preferences, and domain knowledge. ## Supported formats | Format | Extension | What the AI extracts | | ---------------------- | ----------------------- | ------------------------------------------------------------------------ | | **Translation Memory** | `.tmx` | Terminology patterns, consistent style choices, domain-specific phrasing | | **MultiTerm termbase** | `.sdltb`, `.xml` | Term pairs with definitions, domains, usage notes | | **Word document** | `.docx` | Style rules, client preferences, formatting conventions, terminology | | **PDF** | `.pdf` | Style guides, reference material, termbases, specifications | | **Excel / CSV** | `.xlsx`, `.csv`, `.tsv` | Termbases, terminology lists, term pairs | | **TBX termbase** | `.tbx` | Term entries with metadata | | **Plain text** | `.txt` | Notes, guidelines, reference material | ## How to use ### From the SuperMemory toolbar 1. Click the **Distill** button (⚗) on the SuperMemory toolbar in the Supervertaler Assistant panel 2. A choice dialog appears with two options: * **Distill inbox** – automatically distils all non-Markdown files (TMX, DOCX, PDF, XLSX, etc.) currently sitting in the active memory bank’s `00_INBOX` folder. The button shows how many files are available and lists their names. Disabled when the inbox has no distillable files. * **Select files…** – opens a file picker to choose files from anywhere on disk. 3. The AI analyses the content and creates draft articles in the active memory bank’s `00_INBOX` folder 4. Review the draft articles in Obsidian, then click **[Process Inbox](/trados/ai-assistant/super-memory/process-inbox/)** to compile them into the knowledge base Distill always writes into the **active** memory bank – the one currently selected in the toolbar dropdown. To distil into a different bank, switch the dropdown first. ### From the termbase list (shortcut) You can distil a termbase directly from the [termbase settings](/trados/termbase-management/) without exporting it first: 1. Open **Settings → TermLens** to see your termbase list 2. Right-click any Supervertaler or MultiTerm termbase 3. Select **⚗ Distill into memory bank** from the context menu The plugin reads all terms from the termbase, formats them as a structured table, and sends them straight to the Distill pipeline. Draft articles appear in the active memory bank’s `00_INBOX` folder – review them in Obsidian, then run **[Process Inbox](/trados/ai-assistant/super-memory/process-inbox/)** as usual. ## What the AI produces Depending on the source material, Distill creates one or more Markdown articles containing: * **Terminology decisions** — terms the translator consistently chose, with reasoning inferred from context and usage patterns * **Style profile** — register, voice, formatting conventions, and writing patterns observed across the translations * **Client preferences** — conventions specific to the client or project (e.g. “always use ‘Schedule’ instead of ‘Appendix’ in procurement documents”) * **Domain knowledge** — subject-matter conventions, technical vocabulary, and common pitfalls identified from the source material ### Example: Distilling a TMX A translation memory with 10,000 Dutch-English legal segments might produce: * A **terminology article** listing the key legal terms with the translations used and why (e.g. “overeenkomst → agreement (not contract), because the client uses ‘contract’ only for formal notarial documents”) * A **style article** noting the register (formal, third-person, passive voice) and formatting conventions (numbered clauses, capitalised defined terms) * A **domain article** capturing Dutch legal system conventions relevant to translation (e.g. “Dutch notarial acts use specific formulaic language that should be preserved, not naturalised”) ### Example: Distilling a client style guide A 20-page Word document from a client might produce: * A **client profile** with their language preferences, terminology decisions, and contact details * A **style article** with their formatting rules, preferred register, and localisation conventions * A **terminology article** with their approved terms and rejected alternatives ## Tips * **Start with your most important client.** Distill their largest TM first — you’ll immediately see the value as the AI surfaces terminology patterns you may not have been consciously aware of. * **Combine sources.** Select a client’s TM, their style guide PDF, and their termbase Excel file together — the AI cross-references them to produce richer articles. * **Review before processing.** Distill outputs draft articles to the inbox, not directly to the knowledge base. Always review them in Obsidian before running Process Inbox. * **Large files are truncated.** Very large TMX files (100K+ segments) are automatically truncated to fit the AI’s context window. For best results with huge TMs, export a representative subset first. ## See Also * [Process Inbox](/trados/ai-assistant/super-memory/process-inbox/) * [Quick Add](/trados/ai-assistant/super-memory/quick-add/) * [AI Settings](/trados/settings/ai-settings/) # Health Check > Scan and repair a memory bank The **Health Check** button scans the active memory bank for problems and fixes what it can — like a librarian who keeps the shelves organised. ## What it checks * **Conflicting terminology** — the same source term translated differently in different articles * **Broken links** — `[[backlinks]]` that point to articles that don’t exist * **Orphaned articles** — articles that nothing links to (disconnected from the graph) * **Stale content** — articles not updated in more than four weeks that have newer siblings on related topics are flagged, and when a newer article contradicts an older one the older article is flagged as potentially superseded * **Duplicate content** — overlapping articles that should be merged * **Missing cross-references** — terms or domains that should be linked but aren’t * **Low confidence** — articles carrying `confidence: low` in their frontmatter are reported as needing human verification (see [Process Inbox](/trados/ai-assistant/super-memory/process-inbox/#enriched-frontmatter) for the confidence scoring) * **Missing frontmatter fields** — articles created before the enriched-frontmatter schema shipped have missing `tldr`, `confidence`, `sources`, etc. filled in automatically by inferring values from the article content and folder location * **Index accuracy** — the `05_INDICES/` master files (master-terminology, client-summary, domain-summary) are refreshed so they reflect the current contents of the bank ## How it works The AI produces a detailed report in the chat and automatically applies safe fixes (creating stub articles, updating indexes, fixing broken references). Changes that need human judgement are flagged for review. Health Check runs against the **active** memory bank only. If you keep several banks side by side, run it once per bank. ## Completion summary When Health Check finishes, a summary bubble always appears at the bottom of the chat so you know the operation is done: * **“Health Check: applied N changes”** – the AI auto-fixed N files. The summary lists each updated or newly created file. Scroll up to read the full report, and open Obsidian to review the changes. * **“Health Check complete – no changes applied”** – the AI scanned the bank and wrote its report above but did not auto-fix any files. Any issues it flagged are for your review. Caution **Important:** The AI can and will create, update, and reorganise files in the active memory bank when you run Health Check. To stay safe: * **Keep originals elsewhere.** Don’t put your only copy of a termbase or style guide in a memory bank — keep the original in its own folder. * **Back up your memory banks regularly.** Copy the entire `memory-banks` folder to a backup location before running Health Check for the first time, and periodically after that. If something goes wrong, you can simply replace the bank folder with your backup. * **Review changes in Obsidian.** After running Health Check, open Obsidian and browse the recently modified files to verify the AI made sensible changes. Obsidian’s search and graph view make this easy. ## See Also * [Process Inbox](/trados/ai-assistant/super-memory/process-inbox/) * [Distill](/trados/ai-assistant/super-memory/distill/) * [SuperMemory](/trados/ai-assistant/super-memory/) # 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 directly into a memory bank’s inbox. 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:** `00_INBOX` * **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 drops straight into that bank’s inbox. Next time you click **[Process Inbox](/trados/ai-assistant/super-memory/process-inbox/)** with that bank active in the toolbar, the AI organises it into structured articles. ## 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/) * [Process Inbox](/trados/ai-assistant/super-memory/process-inbox/) * [User Data Folder](/trados/data-folder/) # Process Inbox > Organise raw Markdown notes into structured knowledge base articles The **Process Inbox** button in the Supervertaler Assistant toolbar reads raw Markdown notes from the active memory bank’s `00_INBOX/` folder and uses AI to organise them into structured knowledge base articles – client profiles, terminology entries, domain knowledge, and style guides. ## How to use 1. Drop **Markdown notes** into the active memory bank’s `00_INBOX/` folder: client briefs, termbases, feedback notes, style guides, reference articles, or anything else you have written down as plain `.md` text. 2. Open the **Supervertaler Assistant** panel and look for the SuperMemory toolbar below the context bar. 3. The toolbar shows how many files are waiting in the active bank (e.g. “3 files in inbox”). 4. Click **Process Inbox**. 5. The AI reads each Markdown file, creates structured articles in the appropriate folders, and archives the originals to `00_INBOX/_archive/`. A summary of all created files appears in the chat when processing is complete. ## Markdown only – use Distill for everything else Process Inbox is a Markdown compiler. It reads `.md` files and writes structured `.md` articles. It does **not** read translation memories, termbases, Word documents, PDFs, or spreadsheets. For any file that is not plain Markdown, use [**Distill**](/trados/ai-assistant/super-memory/distill/) instead – it knows how to extract knowledge from binary formats and writes its output as Markdown into the same `00_INBOX/` folder, ready for Process Inbox to compile. If you drop a non-Markdown file (e.g. a `.tmx` or `.pdf`) into the inbox folder by mistake, the inbox count still includes it – so the Process Inbox button lights up – but clicking the button shows a message pointing you at Distill instead. Process Inbox will not silently ignore your file, and it will not crash trying to compile a binary blob as Markdown. Obsidian plugin sidecar files (currently `.edtz`) are a special case: they are editor metadata, not knowledge content, so they are skipped silently by both Process Inbox and Distill. They do not count towards the inbox total and they do not trigger the “non-Markdown files” warning. | You have… | Use this | | ------------------------------------------------------------------------------------ | --------------------------------------------------------------------------- | | A Markdown brief, termbase, feedback note, or anything plain-text you wrote yourself | **Process Inbox** | | A `.tmx` translation memory | **Distill** | | A `.docx` style guide or client briefing | **Distill** | | A `.pdf` reference document | **Distill** | | A `.xlsx` / `.csv` termbase | **Distill** | | A `.sdltb` MultiTerm termbase | **Distill** (right-click in TermLens settings → *Distill into memory bank*) | | A `.tbx` termbase | **Distill** | The two features compose: run Distill on your binary files first, review the draft `.md` articles it produces in the inbox, then run Process Inbox to compile them into the structured knowledge base. ## What gets created Depending on the content of your raw material, Process Inbox creates articles in one or more of these folders: | Folder | Article type | Example | | ---------------- | ---------------- | -------------------------------------------------------------- | | `01_CLIENTS` | Client profiles | Language preferences, terminology decisions, contact details | | `02_TERMINOLOGY` | Term articles | Approved translations with rejected alternatives and reasoning | | `03_DOMAINS` | Domain knowledge | Conventions, common pitfalls, reference material | | `04_STYLE` | Style guides | Formatting rules, register, localisation conventions | Each article includes rich YAML frontmatter with metadata and backlinks to related articles, building up an interconnected knowledge graph. The frontmatter fields are: | Field | Purpose | | --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `type` | Article type – `terminology`, `client`, `domain`, `style`, or `template` | | `domain` | Subject area (e.g. Legal, Medical, Marketing) | | `client` | Client name when applicable | | `language_pair` | Source → target language codes | | `confidence` | `high` / `medium` / `low` – set by the AI based on the authority of the source material. Low-confidence articles are flagged for human review by [Health Check](/trados/ai-assistant/super-memory/health-check/). | | `sources` | Original filenames the article was derived from, for traceability. Terminology articles always quote exact source and target terms verbatim. | | `tldr` | One-sentence summary for fast scanning in Obsidian previews and the master indices below | | `created` / `updated` | Timestamps maintained automatically | ## Automatic indexes After every successful Process Inbox run, three master index files are refreshed in the bank’s `05_INDICES/` folder: * `master-terminology.md` – a flat table of all source → target term decisions across the bank, with domain, client, confidence, and status columns * `client-summary.md` – one section per client with their `tldr` or first paragraph * `domain-summary.md` – one section per domain with their `tldr` or first paragraph These indexes are built by scanning frontmatter directly – no extra LLM call – and complete in under a second. Open them in Obsidian to browse the whole bank at a glance. [Health Check](/trados/ai-assistant/super-memory/health-check/) refreshes them as well. ## Templates and the heal-on-activation prompt Process Inbox is driven by an AI prompt that lives inside the active memory bank at `06_TEMPLATES/compile.md`. Health Check uses a sister file at `06_TEMPLATES/lint.md`. Both files are bundled with the plugin and copied automatically into every newly created bank, so a fresh bank works out of the box. If you switch to an older bank that does **not** have these template files (for example, a bank you created before the template-bundling feature shipped, or a bank where you accidentally deleted one of them), the plugin notices the gap and offers to restore the missing files from its built-in defaults. You will see a small dialog titled *“Missing memory bank templates”* listing the missing files with **Yes / No** buttons. Click **Yes** to restore them and Process Inbox / Health Check immediately become usable on that bank. Click **No** if you have a reason to want the templates absent (e.g. you are intentionally disabling those features for that bank), and the plugin will leave the bank as-is. The restore is non-destructive: existing template files in the bank are never overwritten, only missing ones are added. Your edits to template files are per-bank and safe. ## See Also * [Distill](/trados/ai-assistant/super-memory/distill/) – extract knowledge from translation files (TMX, DOCX, PDF, termbases) * [Health Check](/trados/ai-assistant/super-memory/health-check/) – scan and repair the active memory bank * [SuperMemory](/trados/ai-assistant/super-memory/) – overview of SuperMemory and memory banks * [Obsidian Setup](/trados/ai-assistant/super-memory/obsidian-setup/) – installing Obsidian and the Web Clipper # Quick Add (Ctrl+Alt+M) > Capture terms, translations, and knowledge while translating While translating in Trados, you can instantly capture a term, a translation pair, or a free-form note to the active memory bank – and optionally inject it into your active translation prompt so the next Ctrl+T picks it up immediately. ## How to use 1. In the Trados editor, select the source text you want to capture (optional – the full source segment is used if nothing is selected) 2. Press **Ctrl+Alt+M** or right-click and choose **Add to memory bank** 3. Fill in the dialogue: * **Source term** – the source-language term (pre-filled from your selection). The label shows your project’s source language, e.g. “Source term (Dutch):” * **Target term** – the target-language translation (pre-filled from target selection, if any). The label shows your project’s target language, e.g. “Target term (English):” * **Notes** – optional context, alternatives, or client preferences * **Save as raw note** – when ticked, the entry goes to `00_INBOX/` as a free-form note for the AI to compile via [Process Inbox](/trados/ai-assistant/super-memory/process-inbox/) rather than directly to `02_TERMINOLOGY/` as a structured article. Useful when the knowledge is ambiguous or context-dependent (e.g. “fiche can mean either sheet or plug depending on context”) * **Also append to active translation prompt** – when ticked, a row is added to the TERMINOLOGY table in your [active prompt](/trados/ai-assistant/super-memory/active-prompt/) so the translation takes effect immediately (only available in structured article mode, not raw note mode) 4. Click **Add** The entry lands in whichever memory bank is currently selected in the toolbar dropdown. To capture into a different bank, switch the dropdown first and then press Ctrl+Alt+M. ## Two save modes ### Structured article (default) When “Save as raw note” is **unchecked**, Quick Add creates a finished Markdown article directly in the active memory bank’s `02_TERMINOLOGY/` folder with YAML frontmatter (source term, target term, domain, status, date). The article is immediately available to the AI on the next translation – no Process Inbox step needed. The filename uses the format `source term → target term.md` (e.g. `fiche → plug.md`). ### Raw note When “Save as raw note” is **checked**, Quick Add writes a free-form Markdown note to `00_INBOX/` instead. The note contains whatever you entered in the source, target, and notes fields, timestamped and labelled as a Quick Add capture. Run [Process Inbox](/trados/ai-assistant/super-memory/process-inbox/) to have the AI compile it into one or more structured articles. This mode is useful when: * The knowledge doesn’t fit a clean source → target pair (e.g. a term with multiple context-dependent translations) * You want to capture a general observation or client preference rather than a specific term * You’d rather let the AI figure out the right article structure ## See Also * [Active Prompt](/trados/ai-assistant/super-memory/active-prompt/) * [Process Inbox](/trados/ai-assistant/super-memory/process-inbox/) * [SuperMemory](/trados/ai-assistant/super-memory/) # Supervertaler Bridge The **Supervertaler Bridge** is a pair of small localhost-only HTTP services – one in each product – that let Supervertaler for Trados and Supervertaler Workbench cooperate while you translate. Each bridge runs in the background, exposes a few endpoints on `127.0.0.1` only, and is gated behind a per-session bearer token. The two directions are independent and either side can be used without the other: * **Trados → Workbench (read context).** The Trados plugin exposes the active project’s segment, TM matches, termbase hits, and surrounding context so Workbench’s floating Sidekick Chat can answer questions about your real Trados work. * **Workbench → Trados (route QuickLauncher).** Workbench exposes a single endpoint that lets the Trados plugin push a [QuickLauncher](/trados/quicklauncher/) prompt into Sidekick Chat – the response then appears in Sidekick instead of in the Trados Assistant. The rest of this page covers the Trados-side bridge first (the read direction, which has been around longer), then the Workbench-side bridge (the QuickLauncher-routing direction). ## Trados-side bridge: read project context ### What it does When Supervertaler Workbench’s Sidekick Chat is asked a question (with the **🔗 Trados** chip on), it asks the bridge for a snapshot of the current project state. The snapshot contains: * The active source segment and your current target draft * A few surrounding segments (default 5 before and 5 after) * TM matches Trados has found for the active segment * Termbase hits from your enabled termbases * Project name, file name, source and target language This is the same context the in-Trados Supervertaler Assistant chat already uses for its own answers — the bridge just exposes it to the Workbench client. The bridge also accepts an “insert translation” command from the Workbench client, so a future build of Workbench Sidekick will be able to drop AI-suggested translations directly into your active Trados target cell. ### When it runs The bridge is started automatically by the Supervertaler Assistant panel when **all** 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. The hidden setting `AiSettings.SidekickBridgeEnabled` in `settings.json` is `true` (the default). 3. 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. The bridge is stopped automatically when Trados Studio exits. If Trados crashes or is force-killed, the next start of Trados detects the stale handshake file and replaces it with a fresh one. ### 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. ### How to disable The bridge has no UI checkbox – it’s a hidden setting. To disable it entirely: 1. Close Trados Studio. 2. Open `~/Supervertaler/trados/settings/settings.json` in a text editor. 3. Find or add the field `"sidekickBridgeEnabled": false` inside the `aiSettings` object. 4. Save and restart Trados. With this setting off, no bridge listener is started, no handshake file is written, and Workbench Sidekick will not detect a Trados plugin to talk to. ### 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. | | `guard: AiSettings.SidekickBridgeEnabled=false` | You’ve explicitly disabled the bridge in settings.json. | | `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. Workbench Sidekick should detect it within \~3 seconds of opening the chat tab. ### Endpoint reference (advanced) For developers who want to integrate other tools with the bridge, here’s the wire protocol. **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": "BRANTS-CARG-001", "fileName": "20260331 CARG-003-BE-EP 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" } ``` *** ## Workbench-side bridge: route QuickLauncher to Sidekick The Workbench-side bridge is the inverse of the one above: instead of exposing Trados context for Workbench to read, it lets the Trados plugin **push a QuickLauncher prompt into Workbench’s Sidekick Chat**. The response then renders in Sidekick instead of in the in-Trados Assistant. This is the bridge that makes the **QuickLauncher prompts go to: Workbench Sidekick** option in [AI Settings](/trados/settings/ai-settings/#quicklauncher-prompts-go-to) actually do something. ### When it runs The Workbench-side bridge is started automatically by Workbench when its **Sidekick** is initialised (i.e. as soon as Workbench is running with Sidekick available). It writes its own handshake file at `~/Supervertaler/workbench/runtime/sidekick-bridge.json` and is stopped when Workbench exits. The Trados plugin discovers this handshake the same way Workbench discovers the Trados handshake: it reads the file, validates the PID is alive, and posts a Bearer-authenticated HTTP request. ### What happens on a QuickLauncher click When you press Ctrl+Q in Trados, pick a prompt, and have **Workbench Sidekick** selected as the target: 1. The Trados plugin expands the prompt’s variables (selection, surrounding segments, TM matches, project text, etc.) exactly as it would for the in-Trados Assistant. 2. It calls Windows’ `AllowSetForegroundWindow` with the Workbench PID so Sidekick is allowed to come to the front, then POSTs the expanded prompt to the Workbench bridge. 3. Workbench’s Sidekick window pops forward, maximises to the screen it’s on, switches to the Chat tab, echoes the display version of the prompt as a “user” message, and sends the full expansion through Sidekick’s normal LLM pipeline. 4. The response renders in Sidekick. The window stays on top throughout (Sidekick uses a topmost-flip + AttachThreadInput trick to defeat the Windows foreground lock when the response arrives). ### Fallback when Workbench isn’t running If Workbench isn’t running, the handshake file is missing, the PID is stale, or any HTTP error fires, Trados silently falls back to the in-Trados Assistant. Your prompt is never lost – it just lands where it always used to. ### Endpoint reference (advanced) #### `POST /v1/run-prompt` Runs a QuickLauncher prompt in Sidekick Chat. Authentication via `Authorization: Bearer ` from the Workbench-side handshake file. Request body: ```json { "prompt": "", "displayPrompt": "", "promptName": "Explain selection (in general)" } ``` `displayPrompt` is what the user sees as their own message in Sidekick. It’s typically a shortened form of `prompt` (e.g. `[source document — 173 segments]` instead of the full project text) so the chat doesn’t get spammed with the kilobytes of context the LLM needs. Response on success: ```json { "ok": true } ``` Response on failure: ```json { "ok": false, "error": "" } ``` #### `GET /v1/ping` Cheap health check. No authentication required because the response carries no privileged information. ```json { "ok": true } ``` ### Troubleshooting The Workbench-side bridge writes its own diagnostic log at `~/Supervertaler/workbench/runtime/sidekick-bridge.log` – truncated on every Workbench start. Each accepted prompt logs a line like: ```plaintext [2026-05-02 22:29:44.634588] POST /v1/run-prompt accepted (name='Explain selection (in general)', prompt=86 chars, displayPrompt=86 chars) ``` If you’ve set the QuickLauncher target to Workbench Sidekick but nothing’s appearing in Sidekick: 1. Check that Workbench is actually running. 2. Check that `~/Supervertaler/workbench/runtime/sidekick-bridge.json` exists and contains a `port`, `token`, and a non-zero `pid`. 3. Trigger a QuickLauncher prompt, then check the bridge log for an `accepted` line. If the line is there, the prompt was delivered – the issue is on the Sidekick render side. If it isn’t, the Trados-side request never arrived (most likely cause: Workbench was started after Trados, so Trados is using a stale handshake; restart Trados). *** ## Related pages * [QuickLauncher](/trados/quicklauncher/) – the action that drives the Workbench-side bridge * [Supervertaler](/trados/ai-assistant/) – the in-Trados chat that uses the same context fields the Trados-side bridge exposes * [Chat – Trados-aware mode (Workbench)](https://docs.supervertaler.com/workbench/ai-translation/chat/) – the primary consumer of the Trados-side bridge * [User Data Folder](/trados/data-folder/) – where both handshake files live # 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 (Ctrl+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!” ### Clearing Results Click the **Clear** button at the top of the Reports tab to remove all results and start fresh. ### 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 keeps its **Ctrl-tap** trigger; you can reassign a key to 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. ### 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/) * [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 | | **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. ### 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 (Ctrl+T) Press **Ctrl+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 Ctrl+T. Ctrl+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 translation is written directly into the target cell 4. Inline tags (bold, italic, field codes, etc.) are preserved in the translation ### 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/) # 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) – it’s the only supported install channel. Every published build is RWS-signed, which avoids the “Unsigned Trados Studio Plug-in Found” warning that would otherwise appear when Trados loads a plugin from a different source. 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. **“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`, `Ctrl+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`): | Folder | Path | | --------- | ---------------------------------------------------------- | | Roaming | `%AppData%\Trados\Trados Studio\18\Plugins\Packages\` | | Local | `%LocalAppData%\Trados\Trados Studio\18\Plugins\Packages\` | | All users | `%ProgramData%\Trados\Trados Studio\18\Plugins\Packages\` | 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 | | `Ctrl+Q` | View Internally Source | 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+N` | `Control+Option+N` | Quick-add non-translatable term | | `Ctrl` (tap) | `Control` (tap) | Toggle the floating **TermLens popup** (open / close) | | `Ctrl+Shift+P` | `Control+Shift+P` | Open **TermPicker** (list-based) | | `Alt+1` … `Alt+9` | `Option+1` … `Option+9` | Insert term 1–9 by badge number | ## AI Translation | Shortcut (Windows) | Shortcut (Mac) | Action | | ------------------ | -------------- | ------------------------------------------------------------ | | `Ctrl+Q` | `Control+Q` | Open QuickLauncher prompt menu | | `Alt+T` | `Option+T` | Translate the active segment (uses Batch Translate settings) | ## Voice Commands | Shortcut (Windows) | Shortcut (Mac) | Action | | ------------------ | ------------------ | --------------------------------------------------------------------------------------------------------------- | | `Ctrl+Alt+V` | `Control+Option+V` | 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 | ## 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, AI-maintained 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?** Claude Desktop is fully supported and is the recommended app. Other MCP clients that run **local (STDIO) MCP servers on your own machine** – such as Claude Code – also work. **ChatGPT’s desktop app is not supported**: it runs MCP servers in a cloud environment rather than on your computer, so it cannot reach the Supervertaler bridge, which is local to your machine by design (your project never leaves your PC). This is a difference in how the two apps are built, not something the plugin can change. 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.  Asking the AI 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. ## 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.” 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)* | | `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)* | | `search_tm` | Search your Supervertaler (Workbench-bridged) translation memories | | `lookup_term` | Look up a term in your termbases (exact first, then substring matching) | | `find_inconsistencies` | Repeated source segments whose translations differ *(v18.20.95)* | | `check_numbers` | Translated segments whose numbers differ between source and target *(v18.20.95)* | | `check_tags` | Translated segments with missing or extra inline tags *(v18.20.95)* | | `check_terminology` | Translated segments that don’t use the termbase’s expected translation *(v18.20.95)* | | `list_resources` | The TMs and termbases attached to your project and Supervertaler setup *(v18.20.95)* | | `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 source/target pair to your Write termbases | | `update_term` | Fix an existing entry in your Write termbases – exact-match, all other fields preserved *(v18.20.113)* | | `delete_term` | Remove an entry from your Write termbases – destructive, so the AI confirms first *(v18.20.113)* | | `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 | | `run_verification` | Run Studio’s Verify Files (QA Checker) and return the findings per segment | | `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)* | > 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.** * Updates are limited to 200 segments per call; larger jobs are processed in reported batches. * 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. ## 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.  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)* ### 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)* * “Run all your QA checks and give me a report.” * “…then align them all to the best version.” (pairs with the write tools) ### Resources * “Which TMs and termbases is this project using?” *(from v18.20.95)* ### 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 the Supervertaler Workbench): * “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.” 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. **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`. This works for clients that support local STDIO MCP servers in their normal chat (see the note at the top about ChatGPT). 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). * Claude Desktop (recommended), or another MCP client that runs local STDIO servers on your own machine. Note that this means a **desktop** app that executes the server locally – the claude.ai *website* and ChatGPT’s desktop app cannot reach a local MCP server (see the note at the top of this page). * Windows (the MCP server is a self-contained exe; no additional runtimes needed). ## Troubleshooting * **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). * **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 `Ctrl+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. ### Keyboard shortcut | Shortcut (Windows) | Shortcut (Mac) | Action | | ------------------ | -------------- | ------------------------------ | | `Ctrl+Q` | `Control+Q` | Open QuickLauncher prompt menu | Caution Trados Studio assigns `Ctrl+Q` to **View Internally Source** by default. To use `Ctrl+Q` for QuickLauncher, go to **File → Options → Keyboard Shortcuts**, search for **View Internally Source**, and remove or reassign its shortcut. ### 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 `Ctrl+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 Workbench QuickLauncher prompts live in the shared `prompt_library` folder used by both Supervertaler for Trados and Supervertaler Workbench. Any prompt you create in one application is immediately available in the other. ### Routing prompts to Workbench Sidekick By default, a QuickLauncher prompt’s response appears in the in-Trados **Supervertaler** chat panel. You can also have it land in **Supervertaler Workbench’s Sidekick Chat** instead. Open **Settings → AI Settings** and find the **QuickLauncher prompts go to:** dropdown. Pick: * **In-Trados AI Assistant** (default) – existing behaviour, prompt and response stay in the Trados Assistant chat. * **Workbench Sidekick** – the prompt is sent to Supervertaler Workbench over a localhost bridge. The Sidekick window pops forward, maximises to the screen it’s on, switches to the Chat tab, and runs the prompt there. When to pick which: * **In-Trados Assistant** keeps everything in one window and is the right choice if you want chat history to stay alongside the segment you’re translating. * **Workbench Sidekick** gives you a much larger reading area – useful for prompts whose responses are multi-paragraph explanations, full translation comparisons, or anything you want to read without squinting at the narrow Assistant panel. ### Sending prompts to the clipboard (paste into claude.ai, ChatGPT, etc.) Each QuickLauncher prompt can be configured to offer a **Copy to clipboard** destination alongside the usual **Send to Assistant** behaviour. This is useful when you want to paste the fully-expanded prompt – with all `{{SOURCE_SEGMENT}}`, `{{PROJECT}}`, `{{TM_MATCHES}}` etc. already filled in – into an external chat such as a [claude.ai project](https://claude.ai/), ChatGPT, or Gemini. A common workflow: keep an ongoing project on claude.ai for the document you’re translating (with your style guide and reference material attached), and use a QuickLauncher prompt to send the active segment, surrounding context, and TM matches to that project with one keystroke. #### Enabling clipboard mode for a prompt 1. Open **Settings → Prompts** and double-click the QuickLauncher prompt you want to configure (or create a new one) 2. In the Prompt Editor, find the **Mode** row 3. Tick **Copy to clipboard** alongside (or instead of) **Send to Assistant** 4. If both are ticked, pick which one should be the **Default** from the dropdown 5. Click **Save**  The Mode row in the Prompt Editor. #### How it appears in the menu * **One mode ticked** – the prompt appears as a flat menu item, exactly as before. Clicking it fires that single mode. * **Both modes ticked** – the prompt appears as a **cascading submenu**. The default mode is shown first; hover or press the right arrow to reveal both options. The submenu items have mnemonic keys, so once a prompt is highlighted you can press: * `S` – **Send to Supervertaler** * `C` – **Copy prompt to clipboard** #### What happens when you pick clipboard The plugin expands every `{{VARIABLE}}` against the current segment, project, and TM context (exactly as it would for the Assistant), then writes the resulting plain text to the Windows clipboard. The menu closes silently – there’s no confirmation toast. Switch to your browser tab and press `Ctrl+V` to paste. #### 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. ## 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 | Description | | ------------------------------ | -------------------------------------------------------------------------------- | | **OpenAI** | GPT-5.5, GPT-5.4 Mini | | **Claude (Anthropic)** | Claude Sonnet 4.6, Claude Haiku 4.5, Claude Opus 4.8 | | **Gemini (Google)** | Gemini 3.1 Flash-Lite, Gemini 2.5 Pro, Gemini 3.1 Pro (Preview), Gemma 4 26B MoE | | **Grok (xAI)** | Grok 4.3 | | **Mistral AI** | Mistral Large, Mistral Small | | **DeepSeek** | DeepSeek V4 Pro, DeepSeek V4 Flash | | **[OpenRouter](#openrouter)** | Access 200+ models from all major providers with a single API key | | **Ollama (Local)** | Run models locally, no API key required | | **Custom (OpenAI-compatible)** | Any provider with an OpenAI-compatible API | ## API key Enter the API key for your selected provider. The key is stored locally and never sent anywhere except to the provider’s API endpoint. ## Model selection A dropdown showing a curated list of recommended models for the selected provider. ### 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. ## AI context 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 | ### AI context (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. #### 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. ### AI context (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/). #### QuickLauncher prompts go to Picks where Ctrl+Q [QuickLauncher](/trados/quicklauncher/) prompts run. | Option | Where the prompt and response appear | | ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **In-Trados AI Assistant** (default) | The Supervertaler Assistant panel in Trados Studio. Same behaviour as before this setting existed. | | **Workbench Sidekick** | Supervertaler Workbench’s floating Sidekick Chat. The window pops to the front and maximises to the screen it’s on, the prompt is echoed into the chat, and the AI’s response appears there instead of in Trados. | The Workbench-Sidekick option is for users who want the bigger reading area Sidekick provides for long explanations, or who prefer to keep all their AI chat history in one product rather than split between Trados and Workbench. If the option is set to **Workbench Sidekick** but Workbench isn’t running (or the [Supervertaler Bridge](/trados/ai-assistant/supervertaler-bridge/) isn’t reachable for any reason), the QuickLauncher silently falls back to the in-Trados Assistant – a missing Workbench never blocks a prompt. ### SuperMemory context These two toggles control whether [SuperMemory](/trados/ai-assistant/super-memory/) knowledge base articles are included in the AI context. #### Include memory bank in AI context When enabled, the AI loads client profiles, domain knowledge, style guides, and terminology reasoning from the active memory bank before every translation and chat message. This gives the AI the *reasoning* behind your terminology 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 articles are 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/) * [Supported LLM Providers (Workbench)](https://docs.supervertaler.com/workbench/ai-translation/providers/) # 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 (`Ctrl+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 Ctrl+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 Ctrl+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 Ctrl+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 (Workbench)](https://docs.supervertaler.com/workbench/termbases/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. # Shared TM Bridge with Workbench The Shared TM Bridge attaches your Supervertaler Workbench translation memories directly inside Trados Studio as a translation provider. No TMX export, no scheduled sync – Trados reads from the same `supervertaler.db` SQLite file Workbench writes, so a TU you confirmed in Workbench five minutes ago shows up in Trados the next time it queries the TM. It’s the same feature on both sides. This page covers the Trados half; the Workbench half lives at [Shared TM Bridge with Trados](/workbench/translation-memory/shared-tm-bridge/). ## Prerequisites * **Supervertaler for Trados** `v4.20.32` or newer installed. * **Supervertaler Workbench** `v1.10.212` or newer (introduces the per-TM Bridge flag). * Both products writing to the same data folder. Default is `D:\Supervertaler\` (or wherever you’ve configured the Workbench data path). * At least one TM ticked as **Bridge** in Workbench’s TMs tab. ## Attaching a bridged TM 1. Open the project in Trados Studio. 2. **Project Settings** → **Language Pairs** → **All Language Pairs** → **Translation Memory and Automated Translation**. 3. Click **Add** → **Supervertaler TM**. 4. The picker dialogue lists every TM you’ve ticked as Bridge in Workbench, filtered to those whose language pair matches your project. Loose matching applies – a TM stored as bare `nl → en` will show up for an `nl-NL → en-GB` project. 5. Tick the TM(s) you want and click **OK**. Multiple bridged TMs can be attached to the same project. Each will show up as a separate row in the Translation Memory list, named e.g. *Supervertaler TM: BRANTS (URSU-008-BE-EP)*. ## What you get * **Exact (100%) matches** in the Translation Results pane, alongside any SDLTMs you have attached. * **Concordance search** – source-side AND target-side – through both Trados’s built-in Concordance window and the SuperSearch tab. Backed by the FTS5 index Workbench maintains. * **Per-hit TM attribution.** With several bridges attached, each match’s origin strip identifies the specific TM it came from – *Supervertaler: BRANTS (URSU-008-BE-EP)* vs *Supervertaler: PATENTS* – so you can tell at a glance which memory contributed which hit. * **Live updates from Workbench.** Confirming a segment in Workbench writes to the same DB Trados reads, so the new TU appears on the next lookup. No sync step. ## What’s NOT in this release * **Write-back from Trados.** The bridge is read-only. When you confirm a segment in Trados, the update goes to your normal SDLTM, not back to the bridged Workbench TM. Round-trip write support will land in a later phase. * **Fuzzy matching.** Only 100% matches are returned from bridged TMs. Sub-100 fuzzies need to come from another provider attached to the project (e.g. your main SDLTM). Bridge-side fuzzy matching will also land later. ## Diagnostics If the bridge isn’t behaving as expected, the plugin writes a verbose diagnostic log to: ```plaintext %TEMP%\supervertaler-tm-bridge.log ``` Every search, every method call from Trados, every error – it’s all in there with timestamps. If you file a bug, attaching that log makes it much easier to diagnose. Common issues: * **Bridged TM doesn’t show up in the picker.** Check that the TM is still ticked as Bridge in Workbench’s TMs tab, and that its language pair matches the project. The picker filters to compatible pairs only. * **Bridge attached but matches don’t appear.** Make sure the TM actually contains TUs for your source segments. Workbench’s own match panel is a good sanity check – if Workbench doesn’t find the TU there, Trados won’t either. * **“This TM is offline” pill.** The TM is still referenced in `.sdlproj` but the Bridge flag has been un-ticked in Workbench. Re-tick it, restart Trados, and the project will pick it back up. ## See also * The matching Workbench-side help page lives at [Shared TM Bridge with Trados](/workbench/translation-memory/shared-tm-bridge/). # 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/) # 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 | | ----------------- | -------------------------------------------------------------------------------------------------- | | **Project files** | The project’s SDLXLIFF files (the default — original SuperSearch behaviour) | | **Files + TMs** | The project files *and* the project’s translation memories, merged into one result list | | **TMs only** | Only the project’s translation memories — a concordance search, like Studio’s built-in Concordance | 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. ### 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 (or, in a TM mode, one TM entry): | Column | Description | | ----------- | ---------------------------------------------------------------------------------------------------------------- | | **File/TM** | The project-file name, or — for TM results — the translation-memory name, shown in blue. Hover for the full path | | **#** | Segment number within the file; for TM results, the concordance match score | | **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.), or “TM” for TM results | ### 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 and TM Selection Two buttons in the search bar let you narrow what SuperSearch looks at — **Files** for the project’s SDLXLIFF files, and **TMs** for the project’s translation memories. 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) Click either button to open its selection dialog: 1. A list shows all the files (or TMs) found in the project, 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 **Files + TMs** modes; the **TMs** filter applies in **Files + TMs** and **TMs only** modes. ## 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) | | **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. * 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 only** to use SuperSearch as a concordance tool, or **Files + TMs** to see project and TM 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 confirmation dialog shows the filename, row count, termbase name, and language pair — check that you are importing into the right termbase 5. A progress bar tracks the import (useful for large termbases with thousands of terms) **File format:** The first row must be a header row. Recognised column headers (case-insensitive): | 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` | | Notes | No | `Notes`, `Note`, `Definition`, `Comment` | | 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 TSV To export all terms from a termbase: 1. Select the termbase in the list 2. Click **Export to TSV** 3. Choose a save location The exported file uses 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]`. The file is UTF-8 encoded with BOM for Excel compatibility. ## 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. ## Distill into a memory bank You can extract knowledge from any termbase and add it to a [memory bank](/trados/ai-assistant/super-memory/) using the **Distill** feature: 1. Right-click a termbase in the list 2. Select **⚗ Distill into memory bank** The AI analyses all terms in the termbase and creates structured articles (terminology decisions, domain knowledge) in the active memory bank’s inbox. See [Distill](/trados/ai-assistant/super-memory/distill/) for full details. *** ## See Also * [MultiTerm Support](/trados/multiterm-support/) * [TermLens Settings](/trados/settings/termlens/) * [Adding & Editing Terms](/trados/termlens/adding-terms/) * [Distill](/trados/ai-assistant/super-memory/distill/) * [Termbase Basics (Workbench)](https://docs.supervertaler.com/workbench/termbases/basics/) # 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. ![]() ### 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 (Ctrl tap) Tap **Ctrl** (press and release without any other key) 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. Tap **Ctrl** again to close. Inside, **Right / Down / Tab** cycle the highlighted match, **Enter** inserts and closes, **Escape** dismisses without inserting. #### TermPicker (Ctrl+Shift+P) For segments with many matches and when a sortable list view is preferable, press **Ctrl+Shift+P** to open [**TermPicker**](/trados/termlens/termpicker/). It shows all matched terms in a searchable list 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).  ### 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 with a distinct yellow highlight in [TermLens (Workbench)](https://docs.supervertaler.com/workbench/termbases/termlens/). ## 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”). Used to filter the SuperMemory knowledge base context to that client’s profile when this term is in scope. | | **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 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** – Ctrl-tap, cycle, Enter, back to typing. No mouse, no menu hunting. ### Opening and closing | Key | Action | | ----------------------- | ------------------------------------------------ | | **Ctrl** (tap) | Toggle the popup (open if closed, close if open) | | **Escape** | Close without inserting | | Click outside the popup | Close without inserting | The popup has no second default shortcut – the Ctrl-tap is its trigger. (Earlier versions listed **Ctrl+Alt+G** as an alternative; that key now belongs to [AutoTagger](/trados/autotagger/). You can assign your own key to the popup in **File → Options → Keyboard Shortcuts** if you’d like one.) A “Ctrl tap” is a press-and-release of the Ctrl key on its own – no other key in between, and held for less than 400 ms. The same memoQ-style trigger that older versions of Supervertaler used to open TermPicker. ### 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 (Ctrl tap) | [TermPicker](/trados/termlens/termpicker/) (Ctrl+Shift+P) | | -------- | ------------------------------------------------------ | --------------------------------------------------------- | | 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** is a compact overlay that shows all matched terms for the current segment in a sortable, keyboard-navigable list. It is useful when [TermLens](/trados/termlens/) shows many matches and you want a quick overview without scrolling.  TermPicker dialogue with all matched terms for the current segment ### Opening TermPicker Press **Ctrl+Shift+P** to open TermPicker. It appears as a floating window above the editor. ### 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. ### Expandable synonyms Terms with multiple translations display a right-arrow indicator (**▸**) next to the term. To expand and see all synonym sub-rows: * Select the row and press the **Right arrow** key * The sub-rows appear below the parent term, showing each available translation Press **Left arrow** to collapse the synonyms again. ### Keyboard navigation TermPicker is designed for fast keyboard use: | Key | Action | | ------------- | --------------------------------------------- | | **0-9** | Type a number to jump directly to that term | | **Enter** | Insert the selected term and close the picker | | **Escape** | Close the picker without inserting | | **Up / Down** | Navigate between terms (wraps around) | | **Right** | Expand synonyms for the selected term | | **Left** | Collapse synonyms | Navigation wraps around: pressing **Down** on the last term jumps to the first, and **Up** on the first jumps to the last. ### Inserting a term You can insert a term in two ways: * **Click** any row to insert that term at the cursor position in the target field * **Press Enter** on the selected row to insert and close The selected translation is placed at the current cursor position in the target segment. Like the TermLens chips, the picker displays and inserts terms with the capitalisation of the segment occurrence (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 * [Adding & Editing Terms](/trados/termlens/adding-terms/) * [TermLens (Workbench)](https://docs.supervertaler.com/workbench/termbases/termlens/) * [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 **Ctrl+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 *** ## 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 `Ctrl+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/) * [Common Issues (Workbench)](https://docs.supervertaler.com/workbench/troubleshooting/common-issues/) # 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+V** (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 | | -------------------------- | ------------------- | -------------------------------------------------------------------------------------------------------- | | ”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` 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 * [Keyboard Shortcuts](/trados/keyboard-shortcuts/) * [TermLens](/trados/termlens/) * [TermPicker](/trados/termlens/termpicker/)