Opened 14 months ago
Last modified 14 months ago
#34867 closed Bug
[Date Input Localization] Accept-Language Header Takes Precedence Over Language Set With Cookie — at Initial Version
| Reported by: | blue-hexagon | Owned by: | nobody |
|---|---|---|---|
| Component: | Internationalization | Version: | 4.2 |
| Severity: | Normal | Keywords: | l10n i18n localization date input form |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
L10n Bug
Accept-Language Header takes precedence over language set with cookie when rendering date input form fields
This is a minimal example of a previously submitted bug - the original issue can be found here: https://code.djangoproject.com/ticket/34853
In the first example, the language and locale is set to en-US but the form fields are localized to da_DK. The docs make no mention that this should be the expected behaviour. I also show that output localizations, such as times and dates strings are localized properly as they should (see green text in images).
Expected formats:
- da_DK uses a dateformat of dd-MM-yyyy
- en_US uses a dateformat of mm/dd/yyyy
Please refer to the Github repository which contains a minimal example with images, as well as the readme, which contains a full analysis with relevant highlights of settings, modelforms and models.