Feature Request: Native Translation for README & Documentation #196611
Replies: 2 comments
-
|
This is a solid feature request — and one that has been discussed in various forms for years. Here are my thoughts: Why this makes senseYou are right that browser translation mangles Markdown. Code blocks, links, inline code, and tables all break because machine translation does not understand Markdown syntax boundaries. A native solution that is Markdown-aware would be genuinely useful. Workarounds available todayWhile waiting for native support, you can automate README translation using GitHub Actions. Here is a practical approach: Option A: Static translation via GitHub ActionsSet up a workflow that watches for changes to
Option B: Link to translation servicesAdd badges to your README that link to Google Translate or DeepL with the page URL pre-filled: Option C: Use GitHub WikiMaintain docs in the repo Wiki which GitHub renders as a separate page — users can browser-translate Wiki pages more cleanly than README source view. What native support should includeIf GitHub builds this, the key requirements are:
I would suggest also posting this in the official GitHub Public Roadmap discussions for more visibility with the product team. |
Beta Was this translation helpful? Give feedback.
-
Why This Matters: Beyond TranslationGitHub's native translation should preserve: ✅ Semantic intent (what I want) Example:
Additional Context: Morphological ProductivityCroatian (i.e.) is highly agglutinative/inflected. This means:
When forced to English, this creative flexibility is lost in translation. A native GitHub translation feature should preserve not just meaning, This benefits all morphologically-rich languages:
PoC explained via native copilot:morphological decomposition:
(without further translation... but a reader gets the idea why AI is superior to any traditional tranlators and hence it's used for writing letters, it's pretty obvious) Result: Structure of 11+ morphemes that's completely transparent even if totally invented / ad hoc fabricated. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
🏷️ Discussion Type
Question
💬 Feature/Topic Area
Other
Body
Built-in Translation Support for README and Documentation Files
Problem / Motivation
GitHub is a global platform, but documentation is overwhelmingly in English.
This creates barriers for contributors and users who are more articulate in
their native language.
Real-world example:
Someone fluent in Croatian might struggle to express nuanced ideas in English
grammar (especially glagolska vremena - verb tenses). A simple Google Translate
workaround exists, but it's:
Proposed Solution
A "Translate" button (or language selector) in the GitHub UI for README
and documentation files, similar to:
This would:
Why This Matters
they can easily understand CONTRIBUTING.md
Alternatives (Current Workarounds)
.mdfiles per language (unsustainable for maintainers)Real-World Example: Multilingual Open Source
This isn't just about English vs. Other Languages.
Consider repositories from:
Current workaround: Users must:
This is a hidden accessibility barrier.
Why Built-in Translation Matters (Not Browser Translation)
Browser translation exists, but:
A native GitHub feature would:
"Translate link" score?
Problem
Look at this workaround (from C64-Nexus project):
🌍 Reading in another language?
.mddocs🎗️ Future: Built-in GitHub Translation
We're advocating for GitHub to add a native "Translate" button (like YouTube has for captions or comments).
Until then, use the links above or any translation tool. There's no penalty for non-English contributions here.
This works, but it's:
Solution
Add a "Translate" button like YouTube has for captions.
Why This Matters (Beyond "Accessibility")
Real story: A Croatian developer can express retro-futuristic ideas more clearly
in their native language. When forced to English, the idea loses texture.
A native translation preserves that intent while making it globally accessible.
Cost of current workaround:
Proposed Implementation
This isn't about replacing maintainer effort – it's about removing invisible overhead.
CC: @github/product-team
Beta Was this translation helpful? Give feedback.
All reactions