Translating Drydock
Translate the Drydock UI through Crowdin or a pull request with the locale files, or contribute README translations through a repository pull request.
Drydock's interface is translated through Crowdin, and the translation project is open to everyone. You can also send a pull request with the locale files directly. English is the source language; every other locale is community-maintained. Translated README files are maintained separately in the repository.
Languages
Drydock ships with 16 languages beyond English: Arabic, German, Spanish, French, Italian, Japanese, Korean, Dutch, Polish, Brazilian Portuguese, Russian, Turkish, Ukrainian, Vietnamese, Simplified Chinese, and Traditional Chinese.
You switch language in the app under Config > Appearance. See UI configuration for the full locale list.
Translate in Crowdin
For UI translation suggestions, you don't need a GitHub account, a checkout, or any build tooling.
- Create a free account and open the Drydock project.
- Pick your language and start translating. Preserve interpolation placeholders such as
{name}exactly as written in the source string. - Save your suggestions. That's the whole loop.
The sync workflow opens a pull request with translated strings. After review and merge, those translations can ship in a release.
Translate through a pull request
If you'd rather work in a checkout, fork CodesWhat/drydock and edit the locale files directly.
-
Branch from the active release branch,
dev/vX.Y, notmain. Set the PR base to that branch when you open it. -
UI strings live in
ui/src/locales/<locale>/, one JSON file per area (for examplecontainerComponents.json). The English files inui/src/locales/en/are the source. Keep every key and every{placeholder}name exactly as it is in English and translate only the values. -
Run the locale tests from
ui/:npm ci npx vitest run tests/i18n --coverage.enabled=falsekey-parity.spec.tsfails on a key that is missing from your locale or that doesn't exist in English.placeholder-parity.spec.tsfails when a translated string drops or invents a{placeholder}. A PR that adds a new English string has to add it to all 16 locales in the same change. -
README translations (
README.de.md,README.es.md,README.fr.md,README.pl.md,README.pt-BR.md,README.zh-CN.md) are hand-edited in the repository and checked by.github/tests/readme-translations.test.ts. Run it from the repository root withnpm run test:workflows.
Crowdin owns the UI locale files and syncs them back as a pull request. A hand edit in the repository can be overwritten by a later sync with whatever Crowdin has stored for that string. If the string exists in Crowdin, save your translation there too so the two stay in step.
Requesting a new language
Want a language that isn't listed yet? Drop a comment on the translations announcement, and we'll add it to Crowdin so you can start translating.
How it works under the hood
The English UI source strings live in ui/src/locales/en/. The UI-only mapping in crowdin.yml connects those JSON files to the 16 non-English locale catalogs. The Crowdin GitHub Action uploads source strings and checked-in translations, then downloads translations into a pull request against the integration branch.
README translations
Translated README.<locale>.md files are maintained in the repository, not through Crowdin. They currently cover German, Spanish, French, Polish, Brazilian Portuguese, and Simplified Chinese. To contribute, update the translated file against the English README.md, preserve its links and structure, and open a pull request following the contribution guide. Repository tests check translated README structure and release information.
Maintainer feature changes
When a feature adds English source keys, maintainers include matching keys in every configured locale in the same reviewed feature PR. The locale-parity tests require complete namespaces and keys. Checked-in translations are not generated Crowdin output and still need wording review; existing translations should not be replaced with English placeholders.
The sync workflow checks out the highest dev/vX.Y integration branch before it uploads anything, so it cannot synchronize keys from an unmerged feature branch. After the feature PR merges, upload_sources and upload_translations make its checked-in source strings and translation candidates available to Crowdin. download_translations then brings Crowdin output back through a separate reviewed PR. Uploading a candidate does not approve it or guarantee that it replaces an existing Crowdin translation.