# Distill **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 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**](/help/features/ai-assistant/super-memory/process-inbox.md) 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. :::note **Ignored sidecar files.** Distill automatically skips Obsidian plugin sidecar files (currently `.edtz`) sitting in the inbox. These are editor metadata that accompany Markdown notes, not knowledge content, so they are neither sent to the AI nor counted in the "Distill inbox" file count. ::: #### From the termbase list (shortcut) You can distil a termbase directly from the [termbase settings](/help/terminology/termbase-management.md) 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**](/help/features/ai-assistant/super-memory/process-inbox.md) as usual. :::note This shortcut is especially useful for MultiTerm termbases attached to your Trados project. Instead of exporting to a file first, you can distil them in one click. ::: ### 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](/help/features/ai-assistant/super-memory/process-inbox.md) * [Quick Add](/help/features/ai-assistant/super-memory/quick-add.md) * [AI Settings](/help/settings/ai-settings.md) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://supervertaler.gitbook.io/help/features/ai-assistant/super-memory/distill.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.