Lowering the barrier: Using Weblate to bring international languages to GitHub UI #208320
Unanswered
PEnzym
asked this question in
Other Feature Feedback, Questions, & Ideas
Replies: 1 comment
|
@PEnzym Opening up GitHub's UI to crowdsourced localization would definitely help lower the barrier for non-English speakers and beginner developers worldwide! Current State of UI Localization on GitHub
Workarounds Available Today
What to Expect NextBecause UI strings affect security-sensitive workflows (like permission settings, billing options, and 2FA prompts), GitHub typically enforces strict internal QA protocols alongside automated i18n pipelines. Sharing this in the Community Discussion is a great way to show product teams the demand for open translation integrations like Weblate! |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Question
💬 Feature/Topic Area
Other
Body
Hi GitHub Community and Product Team!GitHub is the global home for developers, but for many beginners, students, and non-native English speakers worldwide, the lack of localized menus and user interface elements remains a significant barrier to entry. While the official documentation is steadily expanding its language support, the core platform UI remains exclusively in English.I would like to propose a community-driven solution to this: integrating the GitHub UI with an open-source continuous localization platform like Weblate.Why this approach works:Leveraging the Community: Millions of open-source contributors would gladly help translate GitHub's interface into their native languages. Weblate provides an intuitive, web-based UI where translators don't need to touch code or understand Git.Continuous Localization: Platforms like Weblate connect directly to code repositories. When GitHub developers add a new feature or button, the new string is automatically pushed to translators. Once translated, it can be automatically sent back to GitHub as a Pull Request.Low Overhead for GitHub: By crowdsourcing the localization process through a dedicated translation platform, GitHub wouldn't need to hire massive localization teams for dozens of languages. The global community would handle the heavy lifting and peer-reviewing of the translations.The Impact:Introducing crowdsourced localization would make GitHub significantly more accessible to schools, bootcamps, and emerging tech communities across Europe, South America, Asia, and Africa. It would truly democratize access to the world's most important development platform.I would love to hear what the community and the GitHub team think about opening up the UI for international crowdsourced localization. If you support this idea, please leave an upvote!Best regards,
All reactions