#34867: [Date Input Localization] Accept-Language Header Takes Precedence Over
Language Set With Cookie
-------------------------------------+-------------------------------------
Reporter: blue-hexagon | Owner: nobody
Type: Bug | Status: new
Component: | Version: 4.2
Internationalization |
Severity: Normal | Resolution:
Keywords: l10n i18n | Triage Stage:
localization date input form | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Old 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.**
>
> https://github.com/blue-hexagon/dj-L10n_dateinput_bug
New 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
as well as the readme, which contains a full analysis with screenshot
documentation and relevant highlights of settings, modelforms and
models.**
https://github.com/blue-hexagon/dj-L10n_dateinput_bug
--
Comment (by blue-hexagon):
Rearrange a paragraph.
--
Ticket URL: <https://code.djangoproject.com/ticket/34867#comment:1>
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/0107018abddda1d0-6acfb53d-d213-447e-ac69-c9ca4fe1d6a6-000000%40eu-central-1.amazonses.com.
