#16284: djangojs uses en as fallback language rather than projects language code
-------------------------------------+-------------------------------------
Reporter: anonymous | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version: 1.3
Component: | Resolution:
Internationalization | Triage Stage: Design
Severity: Normal | decision needed
Keywords: | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by jeroen.pulles@…):
This piece of code also causes an annoying bug, as I see it:
I have a project with ''nl'' as default language, the source strings are
in ''en_US'' and there are ''en_GB'' translations. As a result this piece
of code has "en_selected" but no catalog named "en" (it's named en_GB,
obviously); Meaning it ends up with an empty translations dictionary for
no good reason.
To my mind, this should be as simple as ''got language code, got catalog
with that language code, i'm done.''
--
Ticket URL: <https://code.djangoproject.com/ticket/16284#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 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 https://groups.google.com/groups/opt_out.
