#31495 closed Bug (fixed)
Documentation issue: The Django admin L10N behavior described in tutorial02 does not match the actual context
| Reported by: | ynyyn | Owned by: | Omkar Kulkarni |
|---|---|---|---|
| Component: | Documentation | Version: | 3.0 |
| Severity: | Normal | Keywords: | documentation, tutorial |
| Cc: | Triage Stage: | Ready for checkin | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | yes | UI/UX: | no |
Description
The tutorial is really great and comprehensive, and I followed it step by step from start to here,
https://docs.djangoproject.com/en/3.0/intro/tutorial02/#start-the-development-server
In start-the-development-server section, it is said:
Since translation is turned on by default, the (admin) login screen may be displayed in your own language, depending on your browser’s settings and if Django has a translation for this language.
My locale language is not English, but the Django Admin did not recognize this thing, and still displayed in English instead of my preferred language, which is not consistent with what the tutorial said.
It seems that automatic localization with user language preference needs middleware 'django.middleware.locale.LocaleMiddleware', but neither the new project template nor the tutorial has configured or mentioned it before.
This mismatch behavior made me confused for a little while. It might be better to make a revision about it.
Change History (7)
comment:1 by , 6 years ago
| Easy pickings: | set |
|---|
comment:2 by , 6 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:3 by , 6 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|---|
| Type: | Uncategorized → Bug |
comment:4 by , 5 years ago
| Has patch: | set |
|---|
comment:5 by , 5 years ago
| Triage Stage: | Accepted → Ready for checkin |
|---|
PR: https://github.com/django/django/pull/12861