#27981: date/time filter docs inaccurate about how localization works
--------------------------------------+------------------------------------
Reporter: Erdem Yılmaz | Owner: nobody
Type: Bug | Status: new
Component: Documentation | Version: 1.10
Severity: Normal | Resolution:
Keywords: template date filter | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by Erdem Yılmaz):
I just wanted to use localization and at the same time set a specific
DATE_FORMAT option instead of the locale one. Your second and third
approaches can be used but they are not too useful beacuse I should find
all date occurances and apply some filters, which is not a general system
wide solution
https://docs.djangoproject.com/en/1.10/topics/i18n/formatting/#creating-
custom-format-files This custom format file structure helped me. Thanks
I just curious about why when USE_L10N is True, all dates and numbers are
now consistently localized by default even if some format setting
(DATE_FORMAT, TIME_FORMAT etc.) is present. In my opininon setting
something explicitly in the settings.py should have higher precedence than
a locale format
--
Ticket URL: <https://code.djangoproject.com/ticket/27981#comment:5>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.6bddb0a807f32677f8965b1bec7e66e3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
