Opened 9 years ago
Closed 9 years ago
#24805 closed Bug (fixed)
Improve makemessages error reporting for invalid locale path
Reported by: | Wim Feijen | Owned by: | nobody |
---|---|---|---|
Component: | Internationalization | Version: | 1.8 |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Ready for checkin | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | yes | UI/UX: | no |
Description
Following https://docs.djangoproject.com/en/dev/topics/i18n/translation/ in a Mezzanine project, I get an error when I run
django-admin.py makemessages -l nl
CommandError: Unable to find a locale path to store translations for file requirements.txt
mkdir locale solves it.
http://stackoverflow.com/questions/24937133/django-commanderror-unable-to-find-a-locale-path-to-store-translations-for-fi
Proposal: update documentation to add an instruction to make a locale directory, (f.e.
mkdir locale) before the command: django-admin.py makemessages -l nl
Change History (5)
comment:1 by , 9 years ago
Component: | Documentation → Internationalization |
---|---|
Triage Stage: | Unreviewed → Accepted |
Type: | Cleanup/optimization → Bug |
comment:3 by , 9 years ago
Triage Stage: | Accepted → Ready for checkin |
---|
comment:4 by , 9 years ago
Summary: | Update translation documentation to add mkdir locale → Improve makemessages error reporting for invalid locale path |
---|
Do your project really have translations outside of apps? I doubt that requirements.txt have translations. So IMHO the bug is that
makemessages
is complaining before having tried to extract strings from files. I'll suggest a patch.