#14461 closed (fixed)
Allow to use other translation languages than just the ones available in Django
| Reported by: | diegobz | Owned by: | nobody |
|---|---|---|---|
| Component: | Internationalization | Version: | 1.2 |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Accepted | |
| Has patch: | no | Needs documentation: | yes |
| Needs tests: | yes | Patch needs improvement: | yes |
| Easy pickings: | no | UI/UX: | no |
Description
Django doen't allow to activate a language available in a project, but that it is not present in the django/conf/locale/.
I've noticed it's because of the check_for_language function.
Not sure if it's the best way to fix it, but I'm providing a patch that can resolve the issue.
Attachments (1)
Change History (10)
by , 15 years ago
| Attachment: | accept_more_langs.diff added |
|---|
comment:1 by , 15 years ago
| Summary: | Accept to use more languages than just the ones available in Django → Allow to use other translation languages than just the ones available in Django |
|---|
comment:2 by , 15 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
comment:3 by , 15 years ago
| Resolution: | wontfix |
|---|---|
| Status: | closed → reopened |
After further discussion with Jannis on IRC, actually this could be an old restriction that might be worth reviewing and possibly removing provided no existing behavior is affected and all the necessary pieces of the user locale language preferences selection are modified accordingly so the translations added using this mechanism are effectively made available.
comment:4 by , 15 years ago
#14530 was about the documentation side of this issue. It was closed in favor of a complete (including documentation fixes) solution to this ticket.
comment:5 by , 15 years ago
| Needs documentation: | set |
|---|---|
| Needs tests: | set |
| Patch needs improvement: | set |
comment:6 by , 15 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
Accepting it after talking to ramiro in IRC.
I know this is a design decision, and has been like this for a long time. This ticket certainly made me ask myself what would be the reason for such a decision. Fortunately the answer is in the docs: http://docs.djangoproject.com/en/1.2/topics/i18n/localization/#how-to-create-language-files (Locale restrictions box).
I will close the ticket for now. Were a patch like this to be accepted it would need to update the documentation and add tests. Also, it seems to me it needs to deal with updating the LANGUAGES setting somehow because adding the translation path to the path search list isn't enough.