#33068: makemessages is inconvenient when overriding default django translations
-------------------------------------+-------------------------------------
Reporter: Satyajeet Kanetkar | Owner: nobody
Type: Bug | Status: closed
Component: | Version: 3.2
Internationalization | Resolution:
Severity: Normal | worksforme
Keywords: makemessages | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Satyajeet Kanetkar):
@Mariusz Felisiak Thanks for the attempt at reproducing, but one
additional step is needed to make the bug re appear.
Before running `compilemessages`/`makemessages` you need to add at least
one custom translation so that gettext actually has reason to modify the
`.po` file.
Simplest would be to add the below snippet at the end of the `urls.py` of
the default scaffolding:
{{{
from django.utils.translation import gettext as _
_("Translate This!")
}}}
And then run the `makemessages` and `compilemessages` steps as mentioned.
You should see the legitimate translations getting commented out.
I will be re-opening the ticket as I am able to reproduce this with the
above minimal code added to a default django project.
--
Ticket URL: <https://code.djangoproject.com/ticket/33068#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.58b27467b605e8ffe796a9db47348d03%40djangoproject.com.
