nr-translation

List Systems

List game systems that have translations, with per-language counts.

Get Stats

Per-language translation stats for one system.

Get Untranslated

Source strings with no translation in this language, from the system's full source-string manifest (the server parses the game's data files itself), so strings nobody has translated in ANY language are included. Mechanically composable strings are skipped by default (get_autofill covers those).

Get Translations

Existing translations for a language. Call this BEFORE translating and reuse its terminology (unit/faction/weapon names, keywords) exactly — 'approved' entries are the authority. Terminology is system- and language-specific; never invent a translation for a game term.

Get Glossary

Inferred glossary for a system+language: recurring game terms (unit/weapon/ability names, keywords) with their established translations, most-used first. Terms are derived from the corpus itself — a short string that occurs inside many others IS a term, and its translation is the entry. Reuse these EXACTLY. Untranslated terms are the highest-value strings to translate first: each one unblocks every string that contains it.

Get Terms In

Glossary terms occurring inside ONE source string, with their established translations. Call this for a string you are about to translate and reuse every translation it returns.

Get Suggestions

Translation-memory lookup for one source string: fuzzy matches against already-translated strings, plus example pairs showing how rare words of the source were rendered elsewhere.

Analyze Autofill

Compositional auto-fill analysis: how many untranslated strings can be composed mechanically from already-translated parts right now (ready), how many more unlock once their dependencies are translated (potential), and which untranslated strings unlock the most fills. Translate those dependencies first, then call get_autofill — never hand-translate strings the machine can compose.

Get Autofill

Composed translations for strings that decompose entirely into already-translated parts ("Heavy, Sustained Hits 1" from "Heavy" + "Sustained Hits"). Returns proposals only — nothing is written. Review them, drop anything wrong, then pass the rest to submit_translations. Re-run after translating dependency strings to harvest newly unlocked fills.

Search Strings

Search source strings and their translations (case-insensitive substring). Use for concordance: check how a term or keyword was translated elsewhere before using it.

Diagnose Translations

Read-only pre-submit check (nothing is written). Reports per string: formatting warnings (whitespace, line count, numbers differing from source, list formatting), unknown keys, and collisions with already-approved translations. Run this before submit_translations and fix what it flags.

Submit Translations

Submit translations (max 200 per call). They land as pending review; approved strings and other people's pending translations are never overwritten (differing submissions become suggestions; you may replace your own earlier submissions). REQUIRED first: call get_translations and match its established terminology. Keep newlines, dice notation (D6, 2D3+1), measurements and game keywords intact; If a game term has no established translation, verify the official localized term online or ask your use