#34602: Fail gettext when no translation file is found or when no msgid is
found in
the given translation file
------------------------------------------------+------------------------
Reporter: Gergely Kalmár | Owner: nobody
Type: Uncategorized | Status: new
Component: Internationalization | Version: 4.2
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
------------------------------------------------+------------------------
Currently gettext simply falls back to inserting its argument when there
is no appropriate translation file or when the translation file does not
contain an appropriate msgid. This can lead to untranslated messages
appearing when developers change a text but forget to run makemessages (or
extract/update their translation files when using Babel).
For this reason it would be preferable if we had the option to fail
gettext and its variants instead of using a fallback. The only exception
is if the current language is the same as the LANGUAGE_CODE setting, in
which case it should be fine to display the argument of gettext as a
fallback.
--
Ticket URL: <https://code.djangoproject.com/ticket/34602>
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/01070188692e6201-f6533be6-4c9b-40f2-a1bd-e6c5669415b0-000000%40eu-central-1.amazonses.com.
