<@U090ER7JPHA> what is the purpose of the README_C...
# slackbot-chatter
b
@nutritious-balloon-65098 what is the purpose of the README_CN.md and README_JA.md files in the repo? We don't have ones for several of the languages but clicking on Deutsch, Espanol, Portugues, etc. still displays a translated version of the README.
n
I'm on it! Mamoodi can track my progress here.
l
I think we can delete these
n
Based on my investigation, I can now provide a clear answer to your question about the README_CN.md and README_JA.md files and how the translation system works. Summary: README Translation System in OpenHands Purpose of README_CN.md and README_JA.md: These files serve as static, manually-maintained translations of the main README.md file into Chinese (Simplified) and Japanese respectively. They exist as standalone files in the repository for users who prefer to access the documentation directly from the GitHub repository rather than through external services. How the translation system works: 1. Dual Translation Approach: ◦ Static files: README_CN.md and README_JA.md are manually created and maintained ◦ Dynamic service: Links like "Deutsch", "Español", "Português", etc. point to
<https://www.readme-i18n.com/All-Hands-AI/OpenHands?lang=xx>
which uses an external service called zdoc (a free GitHub README translation service) 2. Language Coverage: ◦ Static files: Only Chinese (CN) and Japanese (JA) have dedicated README files ◦ Dynamic service: Supports 8 additional languages (German, Spanish, French, Korean, Portuguese, Russian, Chinese, Japanese) through the external zdoc service 3. Why some languages have files and others don't: ◦ The Chinese and Japanese files appear to be legacy or community-contributed translations that were manually created ◦ The other languages rely entirely on the automated zdoc translation service, which generates translations on-demand and keeps them updated automatically 4. User Experience: ◦ When users click "Deutsch", "Español", "Português", etc., they're redirected to zdoc's translated versions ◦ When users access README_CN.md or README_JA.md directly, they get the static, potentially more accurate human translations This hybrid approach provides both the reliability of static files for major languages and the convenience of automated translations for broader language support without requiring manual maintenance of numerous README files. <sub>View full conversation</sub>
b
@nutritious-balloon-65098 please remove these README_CN.md and README_JA.md files and open a pull request.
n
I'm on it! Mamoodi can continue tracking my progress here.
✅ Task Completed Successfully I have successfully removed the legacy README translation files and created a pull request as requested. Changes Made: • ✅ Removed
README_CN.md
(Chinese translation file) • ✅ Removed
README_JA.md
(Japanese translation file) • ✅ Created pull request #11169 at https://github.com/All-Hands-AI/OpenHands/pull/11169 Verification: • ✅ All changes are concise and directly address the user's request • ✅ No extraneous changes were made • ✅ Pre-commit hooks passed successfully • ✅ Changes have been pushed to the remote branch
remove-legacy-readme-translations
• ✅ Pull request created with comprehensive documentation explaining the rationale The legacy static translation files have been removed, and the dynamic translation system via zdoc service remains fully functional for all supported languages. <sub>View full conversation</sub>