i18n and overriding django.auth translations

253 views
Skip to first unread message

paul.c...@ideoba.com

unread,
Sep 2, 2014, 6:26:42 AM9/2/14
to django...@googlegroups.com
I've got some basic translations working in de_de (German), but it seems that django has brought it's own translations along for the ride after I compile.  I has not translated 'Password' in my locale files but DJango is doing it automatically (I assume from the django.admin module?).  That's fine, but is there a way to override this so that my translations in my locale files take precedence?

So if my /locale/de_de/LC_MESSAGES/django.po file contains a translation, it overrides the default 'Passwort' that django is putting in?

Avraham Serour

unread,
Sep 2, 2014, 10:07:13 AM9/2/14
to django...@googlegroups.com
is this a theoretical question or did you try and it is not working?


On Tue, Sep 2, 2014 at 1:26 PM, <paul.c...@ideoba.com> wrote:
I've got some basic translations working in de_de (German), but it seems that django has brought it's own translations along for the ride after I compile.  I has not translated 'Password' in my locale files but DJango is doing it automatically (I assume from the django.admin module?).  That's fine, but is there a way to override this so that my translations in my locale files take precedence?

So if my /locale/de_de/LC_MESSAGES/django.po file contains a translation, it overrides the default 'Passwort' that django is putting in?

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/f5ba28a5-42ef-4cfa-a43b-19977440574b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

paul.c...@ideoba.com

unread,
Sep 3, 2014, 3:04:43 AM9/3/14
to django...@googlegroups.com
Well, it's a real situation - I removed the django.admin app from settings.py and then my translations worked - it's a basic occlusion - the django.admin translations seem to be used before my own translations when django.admin is enabled and my application has strings like 'Password' in them.

For now, as I'm not using the admin interface I've disabled it and it is now all my own translations, but some form of 'override' so that my app translations come before the django.admin builtin translations would be useful for future use.
Reply all
Reply to author
Forward
0 new messages