ar/LC_MESSAGES | ||
ca/LC_MESSAGES | ||
de/LC_MESSAGES | ||
el/LC_MESSAGES | ||
es/LC_MESSAGES | ||
fi/LC_MESSAGES | ||
fr/LC_MESSAGES | ||
id/LC_MESSAGES | ||
it/LC_MESSAGES | ||
ja/LC_MESSAGES | ||
ko/LC_MESSAGES | ||
nb/LC_MESSAGES | ||
nl/LC_MESSAGES | ||
pt/LC_MESSAGES | ||
ru/LC_MESSAGES | ||
sk/LC_MESSAGES | ||
sl/LC_MESSAGES | ||
sr/LC_MESSAGES | ||
sw/LC_MESSAGES | ||
th/LC_MESSAGES | ||
uk/LC_MESSAGES | ||
vi/LC_MESSAGES | ||
zh-hans/LC_MESSAGES | ||
zh-hant/LC_MESSAGES | ||
.gitignore | ||
blender_manual.pot | ||
README.md |
Blender Documentation Translation
Welcome to the project for managing translations for the (Blender User Documentation). We are always looking for more translators!
The Blender Manual itself is written using reStructuredText
(RST)
and is built with Sphinx.
Translations are managed using the popular gettext Internationalization and localization system. This means that strings are extracted to po-files which provide a mapping for translated strings.
If you want to start contributing it is important to first understand how the English manual works.
How to build & edit the docs locally
Before you start contributing it may be helpful to read the style guides which give instructions on how to write with RST and some goals of the manual.
Now that you are familiar with the process, you can get setup, edit, and contribute your changes by following these links:
How to translate the manual
For translations, we use Sphinx’s internationalization package. To get started see the contribution guide for translations.
Links
- Source Files: Translation's Repository (git repository).
- Forum: Documentation category on Developer Talk
- Chat: #translations on blender.chat
- Administrators: @blendify , @fsiddi
*Note: If you are a new translator who wants to start translating a new language that is not listed in this repository, please get in touch on the #translations chat, and we will be glad to set it up for you.
Issues
Translation issues can be reported here.