Opened 18 years ago
Closed 18 years ago
#3084 closed enhancement (fixed)
Be more specific on how i18n and LANGUAGES interact
| Reported by: | Owned by: | hugo | |
|---|---|---|---|
| Component: | Internationalization | Version: | dev |
| Severity: | trivial | Keywords: | |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | no | Needs documentation: | yes |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
I was trying to translate an application to Catalan and django was nicely ignoring me until I found ticket #1215, so please, state clearly on the i18n documentation that whatever you put on settings.LANGUAGES django will only provide translated content if it has that translation for himself (or atleast a fake).
Cheers,
Marc.
Change History (4)
comment:1 by , 18 years ago
| Needs documentation: | set |
|---|---|
| Triage Stage: | Unreviewed → Accepted |
comment:2 by , 18 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:3 by , 18 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
"Django does support" should be "Django does not support"?
comment:4 by , 18 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
Note:
See TracTickets
for help on using tickets.
(In [4707]) Fixed #3084 -- Documented that Django's core must be translated into a
particular locale for application translations in that locale to work.