Tackling Language Barriers in Open Source Docs: A Case Study of openEuler's...
summary
openEuler builds a G11N SIG and hires ~30 active contributors to translate ~200 repos where ~90% of READMEs are Chinese; a CI bot opens translation issues when Chinese sources change, translators use Gitee and a GitHub mirror, and light-PRs let international users edit the website. Teams spend 6–12 months polishing READMEs, use AI for draft translation plus manual editing, publish brochures, tutorials and FAQs, tune SEO, and target developer experience — progress is measurable but release 24.3 exposes a months-long English delay and persistent quality and info‑loss problems.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 6:48openEuler project overview
- 15:31Translation challenges and CI
- 21:16Developer experience with visuals
- 26:57Translation delays and challenges
- 32:03Conclusion
- 33:11Q&A: Workflow and culture
- 38:37Q&A: CI bot and management
- 40:05Q&A: Technical knowledge gaps
- 43:05Q&A: AI translation and glossaries
- 44:14Q&A: AI-based Chinese translations
related talks
22mRe-inventing the Rosetta Stone Together
33mToward the broader globalization of Open Source
34mTranslating open source project documentation by many translators
44mRunning open source community in China, the experiences from openEuler
25mIs React Translated Yet?
14mContributors wanted: encouraging diversity in your OSS project
01mRuth Cheesley shares key insights on communicating with an international team
44mTen Practical Approaches for Building Inclusive Open Source and InnerSource..