#16516: Blocktrans should tolerate bad locale data
-------------------------------------+-------------------------------------
Reporter: simon29 | Owner: nobody
Type: | Status: new
Cleanup/optimization | Component:
Milestone: | Internationalization
Version: 1.3 | Severity: Normal
Resolution: | Keywords:
Triage Stage: Accepted | Has patch: 1
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 1 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Changes (by claudep):
* needs_better_patch: 0 => 1
Comment:
I understand your concern about using the 'en' translation. But I'm
opposed to use the TEMPLATE_STRING_IF_INVALID setting. If a translation
has an error, the logical fallback is to use the original untranslated
string, not the empty string (which is default for
TEMPLATE_STRING_IF_INVALID).
So I will try to improve the patch by replacing the 'en' hardcoded value
by a NullTranslations instance (which corresponds to the original string,
whatever the original language is).
--
Ticket URL: <https://code.djangoproject.com/ticket/16516#comment:4>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
