#1668: Module name doesn't get translated in M-R
----------------------------------+-----------------------------------------
Reporter: Rudolph | Owner: hugo
Type: defect | Status: reopened
Priority: normal | Milestone: Version 0.92
Component: Internationalization | Version: magic-removal
Severity: normal | Resolution:
Keywords: |
----------------------------------+-----------------------------------------
Changes (by hugo):
* resolution: invalid =>
* status: closed => reopened
Comment:
The problem is, the admin doesn't try to translate module names - not even
it's own module names it delivers with django. There was some discussion
about this in the group:
http://groups.google.com/group/Django-
I18N/browse_thread/thread/5f262db230bb393d
This could be incorporated in some way into the basic source - like adding
gettext_noop() calls with the application names to some places, maybe
{{{__init__.py}}} or some other code. It could even be some dummy line in
the model definition - the gettext stuff doesn't care.
The idea is just to put a translation hook into some python file and to
use the translation calls in the admin templates, so that application
names can be translated as other stuff.
The only problem with this - and that's why I not just put in this
solution - is that you would have to write the application name
explicitely somewhere down. Currently it is taken from the module name, so
this would be repetition for the sake of translation.
Comments?
--
Ticket URL: <http://code.djangoproject.com/ticket/1668>
Django <http://code.djangoproject.org/>
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 [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates
-~----------~----~----~----~------~----~------~--~---
