Closed lingxiaoyang closed 7 years ago
@aaboffill
why remove English .po files??
We are using English in the code...
And also, in English .po files, all strings are empty. I don't think they'll be compiled in a later step with "manage.py compilemessages".
We are using English in the code...
And also, in English .po files, all strings are empty. I don't think they'll be compiled in a later step with >"manage.py compilemessages".
@lingxiaoyang let me think about that, maybe there are a good reason to keep the English .po files.
@lingxiaoyang in our methodology of work on sous-chef
we write always the translatable message in English, your proposal to remove the English .po
files sound reasonable for me too... go ahead!!!
@aaboffill I think I may merge this, based on your approval and the support of @erozqba in the issue discussion #703?
Fixes #703 by lingxiaoyang
Changes proposed in this pull request:
django-admin makemessages
command, before an official solution is provided.Status
How to verify this change
python3 src/manage.py makemessages -l fr --no-wrap --add-location=file
. See if it works fine.django.po
files and see if there are any errors. Don't bother withfuzzy
ones as they will be double-checked on Transifex.Deployment notes and migration
none
New translatable strings
Additional notes
none