Source strings
Product strings flow from version-controlled source files into the translation workspace.
LOCALIZATION
One product.
Many languages.
Leviathan is being designed for a structured translation workflow with terminology, context, review, quality checks and release integration instead of scattered copy-paste translations.
Localization Center
Translate with context.
Crowdin-style workflow concept
LANGUAGE PROGRESSDansk
Suggestions · review · approved strings
GLOSSARYShared
QAChecked
RELEASELinked
TRANSLATION PIPELINE
From source string to release.
Translations should move through a predictable review path so launcher, client, website and support terminology stay consistent.
Suggestions
Contributors propose translations with screenshots, context and terminology guidance.
Review
Reviewers and proofreaders approve strings while checking placeholders, tone and consistency.
Release
Approved translations return through pull requests and CI before reaching a product release.
QUALITY
Consistency across every surface.
Translation memory, a shared glossary and automated checks can keep common Leviathan concepts consistent across launcher, client, support and web.
✓TerminologyShared glossary for product names, buttons, errors and technical terms.
✓ContextScreenshots and notes so translators know where each string appears.
✓QAPlaceholder, length, punctuation and formatting checks before approval.
Translation statusExample
EN
EnglishSource language
100%DA
DanishWorkflow preview
PlannedDE
GermanWorkflow preview
PlannedFR
FrenchWorkflow preview
PlannedCOMMUNITY GATEWAY
Discord can coordinate. Translation stays governed.
Language requests, progress updates and translation issue reports can surface through the community while the translation workspace remains the canonical place for actual strings.
Language requests
Request new languages with demand and contributor interest tracked clearly.
Issue reports
Report broken, misleading or overflowing translations with screenshots and product version context.
Progress updates
Show language completion and review status without accepting conflicting translations in multiple systems.
Version branches
Keep translation changes aligned to the product version and release branch they belong to.
Translation contributions are not open yet.
The workflow is being designed before public contribution begins.