option to pass in multiple locales to the compilemessages command, and multiple locales and multiple domains to the makemessages command
I've updated the existing patch (from the ticket), so that it applies cleanly. I've added tests and docs.
Let me know if this is up to scratch!
allow multiple domains and languages for makemessages command; add op…
…tion to pass in multiple language to the compilemessages command
There are already tests in tests/regressiontests/i18n/commands/compilation.py and tests/regressiontests/i18n/commands/extraction.py. You shouldn't create new test files.
move tests into existing test files
give tests more sensible names; add hr locale to properly check compi…
…lemessages without deleting the django.mo in the it language
Merged the changes into the existing files; I also changed one of the tests to not use the it locale, which is used by some other tests
I'd like to be able to use -l de -l en -l es as alternate for -l de,en,es to stay consistent with -n of startproject. The patch is also missing versionadded/changed directives.
add versionchanged directive
@apollo13 I've added the versionchanged directives. The patch already supported specifiying multiple locales through "-l de -l pt -l it"
add myself to AUTHORS
Could you squash those commits into one? Btw do we really need tests/regressiontests/i18n/commands/locale/hr/LC_MESSAGES/django.po -- the locale folder there has already 3 existing locales, could you reuse those?
I need 2 locales with .po files and without .mo files in order to check that the compilation works properly.
Of the existing locales:
'it' has an error in the .po file and doesn't compile to a .mo file (this is intentional)
'fr' already has a commited .mo file
I can remove the hr locale if it is OK to remove the .mo file from the fr locale, however I didn't think that was a good thing to do.
Closing, adapted and committed code from this PR in 6158c79. See https://code.djangoproject.com/ticket/17181#comment:9 for further details.