| Version 3 (modified by , 12 years ago) ( diff ) |
|---|
Summary
This page is a proposal for a workflow to be able to translate Django documentation through po files (and Transifex platform). See also #18108.
Translation storage
Proposal is to store pot files and po translation files in a separate repository (e.g. django-docs-translations). Pot files only take up 4Mb, so considering that for each language, you add ~7Mb, this is too much for the Django main repository.
Workflow
- A modification is done in the /docs dir of Django's repo.
- A
make gettextin the 'docs' directory generates pot files in_build/locale(works already). Those pot files are copied todjango-docs-translations/potsand modifications pushed.
- Transifex downloads new pot files once or twice a day.
- Translators translate strings on Transifex.
- At defined times, translations are fetched from Transifex and pushed to
django-docs-translations/translations/<locale>/*.po.
- Translated docs build:
make translationsindjango-docs-translationsgenerates .mo files.make html LANGUAGE=<locale> TRANSDIR=<path>/django-docs-translations/translations/<locale>/indjango/docs- Built HTML files are pushed online
Issues
- Some strings are not translatable through po files currently. See https://github.com/django/django/blob/master/docs/_ext/djangodocs.py#L128
- Search should probably be limited in the current language (one search index per language)
Note:
See TracWiki
for help on using the wiki.