Language rules and file formats
Regional number formats. Preserved placeholders.
Translate text for the language and region you need. Recognised numbers and dates follow fixed rules; technical placeholders are protected and checked.
Explore format examples
| Value | de-DE | en-US |
|---|---|---|
| Number | 1.234.567,89 | 1,234,567.89 |
| Date | 13.09.2026 | 9/13/2026 |
| Time | 17:30 | 5:30 PM |
| Percent | 12,5 % | 12.5% |
| EUR amount | 1.234,56 € | €1,234.56 |
Your variables stay usable
Recognised placeholders retain their names and types. For ICU messages, branch text is translated and the technical structure is checked.
{name} · {{count}} · %1$s · {price, number}
Check and retry what needs fixing
Missing or technically invalid translations are retried selectively. If errors remain, the file is not released as a finished translation. Budgets and retry counts are limited.
The rule data covers 1,082 language, script and region variants. This is not a claim of linguistically reviewed translation quality for that many languages.
Which content gets translated?
- JSON, ARB, .strings, Android XML, XLIFF
- Translatable text values and segments. Keys and non-text values are preserved; ARB metadata is protected. Existing Android plural branches are translated; missing categories are not added automatically. XLIFF 1.2 and 2.0 are processed. Special JSON catalogue schemas need a dedicated adapter.
- Markdown / MDX
- Recognised paragraphs, headings, lists, tables and link text. Code and technical content are protected. Arbitrary MDX/JSX constructs are not checked by a compiler.
- Word in the browser
- .docx / .docm: Text, tables, headers, footers, footnotes and endnotes. Comments and embedded objects stay unchanged.
- PowerPoint in the browser
- .pptx / .pptm: Slide text and notes. Layouts, masters, charts and SmartArt are not translated.
- Excel in the browser
- .xlsx / .xlsm: Cell text from the shared string table. Inline strings, formulas, sheet names and native numeric/date cells are not translated or reformatted.
- No direct translation adapter yet
- Examples include Apple .xcstrings and .stringsdict, gettext PO, YAML, CSV, Java .properties, .NET .resx, standalone HTML, PDF, OpenDocument and legacy binary Office files. File conversion and direct translation have different format limits.
Office files are processed in the browser workspace. Formatting within individual text sections may be lost. Check the layout and import into your target application before sharing.
What the rules cover and where they stop
- Only unambiguously recognised literals are adjusted automatically. Ambiguous dates, phone numbers and arbitrary technical identifiers are not rewritten by guessing.
- Values and currencies stay the same. No exchange-rate, unit or time-zone conversion is performed. Date rules use the Gregorian calendar.
- Dynamic values remain runtime placeholders. Your application formats them for display. Automatic conversion between printf, ICU and other template languages is not included.
- Structure and placeholder checks do not replace linguistic review or a build with your framework. Wording still depends on language, context and model.
- These examples come from the versioned engine rules. In a translation job, the preview loads rules from your connected engine. Older versions may not provide this preview.