#31540: i18n URLs are not matched against the fallback language.
--------------------------------------+------------------------------------
Reporter: osxisl | Owner: nobody
Type: Bug | Status: new
Component: Internationalization | Version: 3.0
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by osxisl):
Replying to [comment:9 Sjoerd Job Postmus]:
> - Make it configurable whether or not `LocaleMiddleware` should be
lenient in parsing the language from `id-gibberish` to "looks enough like
`id` to me". If we'd change this "hard" from lenient to "must match
strictly" this might break current applications. See the `en-us` vs `en-
gb` example.
I see the solution in implementing something like a standardised
dictionary [https://unicode-org.github.io/cldr-
staging/charts/37/supplemental/language_territory_information.html] where
language codes and territories are predefined, but anyone can add custom
languages and territories to their apps via settings.py.
I think it won't affect the majority of applications, and the affected
ones can add their custom languages in settings. Or for a better backward
compatibility a Boolean variable can be added to settings.py that sets
**lenient/strictl** match.
--
Ticket URL: <https://code.djangoproject.com/ticket/31540#comment:10>
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/064.6d3c512c971bca259b1723b2377cbf64%40djangoproject.com.
