Rooba
/
wagtail
mirror of https://github.com/wagtail/wagtail.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Updated Managing Wagtail translations (markdown)

Matt Westcott 2022-04-13 19:20:42 +01:00
parent 71aff0f917
commit dbefd8bc37
1 changed files with 3 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
Managing-Wagtail-translations.md

@ -44,14 +44,11 @@ All languages with >= 90% coverage should be in the `WAGTAILADMIN_PROVIDED_LANGU
# Generating new source files for translation # Generating new source files for translation
To be done periodically, particularly after any piece of development that involves creating / editing / moving a significant number of translatable strings. Within each submodule with a 'locale' folder (run `find . -name locale` to find them): To be done periodically, particularly after any piece of development that involves creating / editing / moving a significant number of translatable strings. From `scripts`, run:
cd wagtail/wagtailfoo ./rebuild-translation-sources.sh
django-admin makemessages --locale=en --extension=html,txt,py,js
NOTE: `django-admin` is run from the app's root, NOT the 'locale' folder. and commit the updated files to git.
(Specifying js in `--extension` ensures that translations in our JS templates, e.g. /wagtail/wagtailimages/templates/wagtailimages/chooser/chooser.js, are picked up. If in future we eliminate these JS templates, it should be fine to leave the `--extension` switch out here.)
Then, from the root of the Wagtail codebase: Then, from the root of the Wagtail codebase: