Translation Pages and Workspaces
MetalGlot includes dedicated translation pages for structured localization files, plain text, subtitles, Markdown, and image translation. The best results usually come from choosing the workspace that matches your source format instead of forcing everything through raw text.
Available Translation Pages
Section titled “Available Translation Pages”| Page | Use it for | What it preserves |
|---|---|---|
| I18next v4 JSON | Nested i18next locale files | Keys and JSON structure |
| ICU MessageFormat JSON | ICU-based message catalogs | Plurals, selectors, and formatting syntax |
| Flutter ARB | Flutter .arb localization files | Metadata and ICU message rules |
| XLIFF 2.2 XML | XLIFF 2.2 documents | Inline tags and XML structure |
| YAML Localization | YAML locale files | Keys, anchors, and placeholders |
| Fluent (.ftl) | Fluent message files | Terms, attributes, and Fluent syntax |
| Gettext PO | .po translation files | Context, plural forms, and flags |
| Apple XCStrings | Apple string catalogs | Comments, keys, and catalog structure |
| Laravel PHP | Laravel translation arrays | PHP array structure and placeholders |
| Subtitles (SRT/VTT) | Subtitle files | Timing, notes, cue layout, and styling |
| Markdown (.md) | Markdown documents | Links, code blocks, and Markdown formatting |
| Raw Text | Plain strings and freeform paragraphs | Only the text itself |
| Image Contents | Text inside an image region | The rest of the image outside the selected crop |
How To Choose The Right Page
Section titled “How To Choose The Right Page”- Use the page that matches your source file format whenever possible.
- Use Raw Text for quick single strings, paragraphs, or text that does not belong to a structured localization format.
- Use Image Contents only when the source text is inside an image rather than in a text file.
The format-specific workspaces are designed to reduce cleanup work after translation by preserving the structural parts of each file type.
Page-Specific Notes
Section titled “Page-Specific Notes”Raw Text
Section titled “Raw Text”Raw Text is the fastest option for simple input. It is best for testing models, translating short content, or handling text that does not belong to a localization file.
Image Contents
Section titled “Image Contents”Image Contents is different from the text pages:
- It requires a vision-enabled model.
- It translates text from a selected image area.
- It should not be used for ordinary text files.
If vision mode is still enabled after an image task, MetalGlot warns you before you continue with a text workflow.
Language Support Notes
Section titled “Language Support Notes”Some language pairs use direct translation, while others may use a bridge through English for partially supported combinations. MetalGlot handles that workflow inside the app, but the main thing for users is simple: choose the correct page first, then choose the source and target languages that match your task.
Interface Language Is Separate
Section titled “Interface Language Is Separate”Choosing the app interface language is a separate feature from choosing the source and target languages for a translation task.
- Source and target languages control what gets translated.
- The interface language selector changes menus, labels, and dialogs across the app.
- Switching the interface language does not change the active translation pair for your current task.
See Interface Language Selector for the dedicated guide and SVG walkthrough.