Opened 14 years ago
Closed 14 years ago
#14530 closed (duplicate)
specify if new translations to django core can be made in project directory
Reported by: | Arthur Hebert | Owned by: | nobody |
---|---|---|---|
Component: | Documentation | Version: | 1.2 |
Severity: | Keywords: | ||
Cc: | Triage Stage: | Accepted | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
On the documentation page, http://docs.djangoproject.com/en/dev/topics/i18n/localization/, under the title "Locale Restrictions," it says:
If you want to support a locale for your application that is not already part of Django, you’ll need to make at least a minimal translation of the Django core. A good starting point is to copy the Django English .po file and to translate at least some translation strings.
The text should indicate if the new language .po file may be copied to the project directory, or if it needs to be copied to the Django core source directory (e.g. <python-path>/django/conf/locale/).
Change History (2)
comment:1 by , 14 years ago
Triage Stage: | Unreviewed → Accepted |
---|
comment:2 by , 14 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
I will close this as a duplicate of #14461. When that ticket gets solved to not require putting new files under the Django tree to extend the choices of available locales, the respective modifications to the documentation should be included.