Translating AcreetionOS
The OS speaks English natively; the world doesn’t. Translators multiply reach.
What’s translatable (priority order)
-
Wiki top pages — welcome/getting-started/package-management (highest traffic)
-
Install guide — decision-critical moments benefit most
-
Recovery Environment strings (TUI) — panic moments shouldn’t require English
-
Site chrome/landing pages
Admin guide/release notes stay English-only initially — technical churn makes maintenance economics brutal.
Mechanics
Docs side: language modules follow Antora convention — component copies under ~/pages locale variants tracked in the docs repo (see Writing Documentation for AcreetionOS for structure; translation branches named <lang>-l10n).
Tooling strings (recovery TUI etc.) live beside their source repos; gettext-style catalogs where applicable.
Handling technical terms
| Term class | Rule |
|---|---|
Commands/flags/file paths |
NEVER translate — |
Established localized vocabulary |
Follow your language’s established Linux press usage |
AcreetionOS product terms (ACRECOVERY, repo-main) |
Keep English, gloss on first use |
Review & landing flow
-
Fork/branch, translate keeping markup intact (AsciiDoc syntax survives badly through creative editing — preserve structure exactly)
-
Open PR tagged
[l10n] -
Native-speaker reviewer from community signs off (you may BE that reviewer for your language eventually — Governance & Team Structure)
-
Merge → site build includes locale navigation