README Translations (i18n) – Tracking Issue
We are starting an internationalization (i18n) effort to translate the project README.md into any language to make the project accessible to a global audience.
This issue serves as the central coordination and tracking point for all README translation work.
Scope
- Translate
docs/i18n/README.md - Preserve formatting, links, and code blocks
- Add translations using the naming convention below
File Structure
All translations live in docs/i18n/ and follow this convention:
docs/i18n/
├── README.md # Source (English)
├── README.<code>.md # TranslationExamples
README.zh-CN.mdREADME.es.mdREADME.pt-BR.md
Use standard language codes (ISO 639, with region where applicable).
Languages
We welcome translations in all languages.
Each language should:
- Have its own issue
- Be worked on by one contributor at a time
- Result in a single
README.<code>.mdfile
Language issues may be linked here for visibility.
How to Contribute
Check existing issues to avoid duplicate languages
Open a new issue using this title format:
README translation: <Language> (<code>)Comment on the issue to indicate you’re working on it
Submit a PR when the translation is complete
Please work on only one language at a time.
Labels Used
i18n– Internationalization and localization workdocumentation– Documentation-related changeshelp wanted– Open for community contributionsgood first issue– Beginner-friendly translations
Guidelines
- Native or fluent speakers are strongly preferred
- Do not change technical meaning or intent
- Keep structure and tone consistent with the original README
- Maintainers may request review before merging
Thanks for helping make this project accessible to everyone. Questions or suggestions about translations are welcome in this thread.
Source: memvid/memvid