#34853: [Date Input Localization] Accept-Language Header Takes Precedence Over
Language Set With Cookie
-------------------------------------+-------------------------------------
     Reporter:  blue-hexagon         |                    Owner:  nobody
         Type:  Bug                  |                   Status:  closed
    Component:                       |                  Version:  4.1
  Internationalization               |
     Severity:  Normal               |               Resolution:  needsinfo
     Keywords:  l10n localization    |             Triage Stage:
  form input                         |  Unreviewed
    Has patch:  0                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by blue-hexagon):

 Replying to [comment:3 Natalia Bidart]:
 > Hello, thank you for your ticket and all the details!
 >
 > Is there any chance that you could provide a minimal Django project to
 reproduce this report, including the models? The smallest the example, the
 better, to be able to isolate the issue and pursue a ticket resolution.
 Also, could you please try with the latest stable Django (4.2) or the
 latest pre-release (5.0a1)?

 = Minimal Django project which reproduces the bug (Django 4.2) =

 == 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

-- 
Ticket URL: <https://code.djangoproject.com/ticket/34853#comment:4>
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/0107018abe2e8210-5762d305-2d0b-4e3e-a58e-43f232e5631e-000000%40eu-central-1.amazonses.com.

Reply via email to