#14924: I18N looks for translations in the reverse order of the apps
------------------------------------------------+---------------------------
Reporter: vanschelven | Owner: nobody
Status: new | Milestone:
Component: Internationalization | Version: 1.2
Resolution: | Keywords:
Triage Stage: Accepted | Has patch: 1
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 |
------------------------------------------------+---------------------------
Comment (by ramiro):
`14924.2.diff` (ignore the #10765 reference in the ticket description ,
should be #5494) contains a further evolution to the patch that:
* Extends the changes to include building of !JavaScript catalog in the
`javascript_catalog()` view making it more consistent with the one used
for Python/templates code translations (paths listed in LOCALE_PATHS is
taken in account.)
* As per discussion with Jannis and Claude Paroz, starts the deprecation
path for inclusion of translations located under the ''project path''.
The LOCALE_PATH setting can be used for the same task by listing the
filesystem path to the project level translations. Reationale for this:
* The project path has always been an elusive concept (it is actually
the directory containing the settings) and there has been a shift in other
parts of the framework from using it as a reference for location of assets
at runtime.
* It fails when the settings module is a directory (#10765)
* The `project_dir/locale/` subdir can generate spurious error messages
when the project directory is included in the python path (default
behavior of `manage.py runserver`), e.g.:
`/usr/lib/python2.6/gettext.py:49: ImportWarning: Not importing directory
'/path/to/project/dir/locale': missing __init__.py`. See also
http://groups.google.com/group/django-
users/browse_thread/thread/e8bb9089d9e5be60?pli=1
--
Ticket URL: <http://code.djangoproject.com/ticket/14924#comment:5>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
