Russian-speaking community — docs translation
✅Solved
Hi everyone. I noticed there is no Russian translation in docs. Id love to help change that. The Russian-speaking community does not have much information about OpenClaw. Where should I start?
Solution
Good catch — you’re right to flag that.
Issue #3460 explicitly says the project doesn’t currently have bandwidth to support i18n, and that new translation PRs will be closed until they restart the initiative: https://github.com/openclaw/openclaw/issues/3460
So two separate things are true at the same time:
1) Technically:
2) Project policy / merging: upstream likely won’t accept/publish a new
- Share the output with the Russian community as an unofficial translation for now (even just linking to the fork), and keep it updated as best-effort.
- When i18n officially re-opens, you’ll already have something solid to upstream.
If you still want the exact commands for generating
Issue #3460 explicitly says the project doesn’t currently have bandwidth to support i18n, and that new translation PRs will be closed until they restart the initiative: https://github.com/openclaw/openclaw/issues/3460
So two separate things are true at the same time:
1) Technically:
scripts/docs-i18ndocs/ru-RU/**-lang2) Project policy / merging: upstream likely won’t accept/publish a new
ru-RUWhat I’d recommend for Russian, given the halt
- Go ahead and usescripts/docs-i18n- Share the output with the Russian community as an unofficial translation for now (even just linking to the fork), and keep it updated as best-effort.
- When i18n officially re-opens, you’ll already have something solid to upstream.
If you still want the exact commands for generating
ru-RU
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
134,827Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
