#35306: Improve documentation for the various date format settings
-------------------------------------+-------------------------------------
Reporter: Richard | Owner: Lufafa
Type: | Joshua
Cleanup/optimization | Status: assigned
Component: | Version: 5.0
Internationalization |
Severity: Normal | Resolution:
Keywords: LANGUAGE_CODE, | Triage Stage: Accepted
DATE_FORMAT |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Rich):
The proposed change to the LANGUAGE_CODE setting, in context, reads:
A string representing the language code for this installation. This should
be in
standard `language ID format`. For example, U.S. English
is "en-us"'', the default format to use when localization is disabled
with `localize` and `unlocalize` template filter or tag see
`controlling localization in templates`''. See also
the `list of language identifiers` and `/topics/i18n/index`.
That doesn't read well to me, and also doesn't really cover the situation.
I think the first sentence needs to change to make it clear this is a
fallback, e.g.:
A string representing the fallback language code for this
installation.
The line "USE_I18N must be active for this setting to have any effect." is
not true and should be removed I think.
Finally, a third entry could be added to the list of 'purposes', e.g.
If localization is explicitly disabled via the `localize` and
`unlocalize` template filters or tags. See `controlling localization in
templates`.
The proposed change to formatting.txt seems confusing and unnecessary to
me.
--
Ticket URL: <https://code.djangoproject.com/ticket/35306#comment:18>
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/0107018ead92ca45-b5a0176e-284d-4693-b9d2-186528962880-000000%40eu-central-1.amazonses.com.
