#11714 closed (fixed)
Document usage of i18n functions to translate to arbitrary language
| Reported by: | Jarek Zgoda | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | dev |
| Severity: | Keywords: | i18n | |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Documentation for i18n does not mention how to use translation mechanisms to translate to languages other than configured statically (in settings) or discovered by middleware. Attached patch adds section on this use case, additionally documenting usage of django.utils.translation.activate(), django.utils.translation.get_language() and django.utils.translation.check_for_language().
Attachments (2)
Change History (9)
by , 15 years ago
| Attachment: | i18n-docs.diff added |
|---|
comment:1 by , 15 years ago
Please, review the text I provided in patch, English is not my native language.
comment:2 by , 15 years ago
| milestone: | → 1.2 |
|---|---|
| Triage Stage: | Unreviewed → Ready for checkin |
comment:3 by , 15 years ago
| Patch needs improvement: | set |
|---|---|
| Triage Stage: | Ready for checkin → Accepted |
by , 15 years ago
| Attachment: | 11714-r12454.diff added |
|---|
Patch updated to post i18n docs refactor plus some typos.
comment:4 by , 15 years ago
| Patch needs improvement: | unset |
|---|
comment:5 by , 15 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:6 by , 15 years ago
Note:
See TracTickets
for help on using tickets.
missing documentation on few functions from django.utils.translation