Changes between Initial Version and Version 1 of Ticket #26337
- Timestamp:
- Mar 8, 2016, 4:29:34 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #26337 – Description
initial v1 3 3 The issue is exactly at this line https://github.com/django/django/blob/master/django/utils/translation/trans_real.py#L190 4 4 5 And it is currently done this way because django translations does not define values for english variants (see issue https://code.djangoproject.com/ticket/24413 ) because message ids are enough, and such, if fallback language was to be used, all english translations from django would fail when the default language is not english resulting in incorrect translations all over the place.5 And it is currently done this way because django translations does not define values for english variants (see issue #24413 ) because message ids are enough, and such, if fallback language was to be used, all english translations from django would fail when the default language is not english resulting in incorrect translations all over the place. 6 6 7 7 Now the ticket above fixed the issue for django english translations, but actually creates a new issue (the one reported in this ticket).