Settings
Dragoman has two groups of settings:
- Project Settings > Plugins > ta Dragoman: the target, checks, fonts, pseudo-localization, machine translation, the review pass and folders. They are saved in
Config/DefaultEditor.ini, in the[/Script/TADragoman.TADragomanSettings]section. Commit that file so the whole team uses the same settings. - Editor Preferences > Plugins > ta Dragoman: your API keys. They are saved per user and never committed.
Target
Section titled “Target”| Setting | Default | Description |
|---|---|---|
| Target Name | Game |
The localization target to check, as named in Tools > Localization Dashboard. Most projects have one called Game. The panel’s Target menu sets it too, and the commandlet’s -Target overrides it for one run. |
Assets
Section titled “Assets”| Setting | Default | Description |
|---|---|---|
| Scan Assets | On | Look for hardcoded and broken text in Blueprints, Widget Blueprints, data tables and data assets. See Asset checks. |
| Asset Folders | Empty (/Game) |
Content folders checked for hardcoded text, including subfolders. |
| Ignored Asset Folders | Empty | Content folders never checked, for example debug or developer folders. They also apply to Data Validation. |
Checks
Section titled “Checks”| Setting | Default | Description |
|---|---|---|
| Max Expansion | 1.6 |
Warn when a translation is this many times longer than its source. German and Finnish often need 1.3 times the length. 0 turns this check off. Texts with a MaxLength in the notes are checked against that instead. |
| Min Source Length For Expansion | 12 |
Sources with fewer visible characters are not checked for expansion: “OK” to “Einverstanden” is fine. |
| Fonts To Check | Roboto (/Engine/EngineFonts/Roboto) |
The fonts your UI uses. Translations are checked for characters none of them can draw. Composite fonts count with their fallback and sub-font faces. Leave the list empty to skip the check. See Missing glyphs. |
| Rule Levels | Empty | Turn rules off or change their severity, by rule id. See Changing severities. |
Pseudo-Localization
Section titled “Pseudo-Localization”| Setting | Default | Description |
|---|---|---|
| Pseudo Culture | en-XA |
Culture code of the pseudo language. en-XA is the usual pseudo-locale code. It is added to the target when you build it. |
| Pseudo Expansion | 0.35 |
Extra length added to every text, from 0 to 2. 0.35 makes texts 35 % longer. |
| Pseudo Accents | On | Replace letters with accented ones, to find fonts and texts that are not localized. |
| Pseudo Brackets | On | Wrap every text in [ ], so cut-off and concatenated texts stand out. |
See Pseudo-localization.
Machine Translation
Section titled “Machine Translation”The machine translation dialog shows these settings and saves them here when a translation starts.
| Setting | Default | Description |
|---|---|---|
| Machine Preset | Custom |
Fills in the provider, the endpoint and a default model: DeepL (free API key), DeepL (Pro API key), OpenAI, Azure OpenAI, OpenRouter, Ollama (local) or LM Studio (local). Pick Custom to set them yourself. |
| Machine Provider | None |
None, DeepL or OpenAI-compatible. With None, machine translation is off. |
| Machine Endpoint | Empty | The service URL. DeepL: https://api-free.deepl.com/v2/translate with a free key, https://api.deepl.com/v2/translate with a Pro key. OpenAI-compatible: the chat completions URL, for example https://api.openai.com/v1/chat/completions, or http://localhost:11434/v1/chat/completions for a model on your own PC. |
| Machine Model | Empty | OpenAI-compatible only: the model name, for example gpt-4.1-mini or a local model. |
| Project Brief | Empty | What translators need to know about the game, for example “Dark fantasy RPG for adults. Short, punchy UI texts. Players are called Wardens.” Sent with every request (DeepL: as context, which it does not bill). |
| Style Guide | Empty | Style rules, one per entry, for example “Keep button labels under 12 characters”. DeepL gets up to 10 of them (300 characters each). |
| Culture Formality | Empty | Formal or informal address per language, for example de = Informal (du), fr = Formal (vous). |
| Culture Notes | Empty | Extra notes per language, for example ja = “Use katakana for item names”. |
| Send Context | On | Send each text’s asset and location, translator note and maximum length with it. |
| Neighbor Texts | 3 |
Texts around each text (same asset or source file) sent as context, with their translations as style examples, from 0 to 10. |
| Use DeepL Glossary | Off | DeepL only: keep a DeepL glossary with your glossary’s terms and use it. It creates and replaces glossaries in your DeepL account. |
| Machine Batch Size | 25 |
Texts per request, from 1 to 100. |
See Machine translation.
Review
Section titled “Review”| Setting | Default | Description |
|---|---|---|
| Review Pass | Off | After translating, ask a chat service to review each machine translation against the source, glossary, length and style guide. The verdicts and suggestions sort the review queue; nothing is changed automatically. One more request per batch. |
| Review Endpoint | Empty | The review service. Empty: the machine translation endpoint, when it is a chat service. Needed when you translate with DeepL. |
| Review Model | Empty | The review model. Empty: the machine translation model. |
See Review pass.
Data Validation
Section titled “Data Validation”| Setting | Default | Description |
|---|---|---|
| Run During Data Validation | On | Check widgets, Blueprints and tables for hardcoded text when they are saved or validated. |
| Min Validation Severity | Warning |
Findings below this severity are not reported by Data Validation. |
See Data Validation.
| Setting | Default | Description |
|---|---|---|
| Data Directory | Localization/Dragoman |
Glossary, notes, translation memory and review marks. Relative paths start at the project folder. Commit this folder. See Project files. |
| Output Directory | Saved/Dragoman |
Reports (in Reports), translator packages (in Packages), gather logs (in Logs) and the ids of the DeepL glossaries Dragoman made. Relative paths start at the project folder. |
Your API keys
Section titled “Your API keys”Editor Preferences > Plugins > ta Dragoman > Machine Translation (the machine translation dialog’s Editor Preferences button opens it):
| Key | Used for | When empty |
|---|---|---|
| Chat Service API Key | The OpenAI-compatible service. | The DRAGOMAN_API_KEY environment variable. |
| DeepL API Key | DeepL. | The DRAGOMAN_DEEPL_KEY environment variable. A key set in 1.0 (in the Chat Service API Key) still works. |
| Review Service API Key | A separate review service. | The Chat Service API Key. |
The keys are stored in your user settings (EditorPerProjectUserSettings.ini in the project’s Saved folder), not in the project’s config, so they are never committed. The environment variables are the usual way to give a build machine a key. Local services such as Ollama and LM Studio need no key.
The target’s own settings
Section titled “The target’s own settings”The languages, the native language, the gather paths and the target dependencies are not Dragoman settings. They belong to the localization target and are edited in Tools > Localization Dashboard, as before. Dragoman reads them, and changes them in two cases: building the pseudo language adds the pseudo culture to the target, and Repair gather setup fixes the problems you tick, like the Localization Dashboard and the Project Settings do.