Translating Drydock
Help translate the Drydock UI and README files through Crowdin. No GitHub account or build setup required.
Drydock's interface and translated README files are managed through Crowdin, and the translation project is open to everyone. English is the source language; every other locale is community-maintained.
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.
How to contribute
You don't need a GitHub account, a checkout, or any build tooling. Everything happens in Crowdin.
- Create a free account and open the Drydock project.
- Pick your language and start translating. UI strings include surrounding context and often a screenshot; README sections retain their Markdown context.
- Save your suggestions. That's the whole loop.
Translations sync back into the repository automatically. A bot opens a pull request with translated strings, so your work ships in the next release without anyone editing generated translation files by hand.
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/, and the English README source is README.md. Crowdin watches both through the Crowdin GitHub Action, which pushes new source strings and pulls completed translations back as a pull request. The UI supports all 16 non-English locales listed above. README translations currently cover German, Spanish, French, Polish, Brazilian Portuguese, and Simplified Chinese. Don't edit the per-language JSON files or translated README files directly; translate in Crowdin and let the sync handle the generated files.