django internationalization and translations issue

13
votes

I have a problem with django translations.

Problem 1 - I updated string in django.po file, but the change does not appear on the webpage.

Problem 2 - I have created my own locale file with django-admin.py makemessages -l et, added the translation string into file, but they too do not appear on the page.

I do not think this is setting problem, because the translations from django.po file do appear on the website, its just the changes and the translations from my own generated file that do not appear.

Edit: My settings.py contains this:

gettext = lambda s: s
LANGUAGE_CODE = 'et'

LANGUAGES = (
             ('et', gettext('Estonian')),
             )

my own locale files are in

/path/to/project/locale/et/LC_MESSAGES/

and the files are

django.mo and django.po

the file I refer to in problem 1 is django own et transaltion, which I changed.

7
djangointernationalizationtranslation
Are you ready the doc about i18n? I'm guessing, but do you enable i18n tag in templates? Are you sure your .po file is in the right path? Can you write more info? – diegueus9
Well yes. i18n is enabled in templates with {% load i18n %}. Since the django.po file is in correct path (problem 1) i dont think its the problem of either enabling or loading i18n. Since like i said - existing translations are beeing loaded into template. But how do i know if the problem 2 locale files are in correct place? They are in the place where they were generates by django-admin.py makemessages -l et – Odif Yltsaeb
read this: docs.djangoproject.com/en/1.1/topics/i18n/localization/… the path will be: your_project/locale/et/LC_MESSAGES/django.po. – diegueus9
Well, thats exactly where my self generated files are, so whats the problem? – Odif Yltsaeb
again, i'm guessing, do you compile your .po file? are you sure yo don have problems with the .po file? – diegueus9

7 Answers

25
votes

Well, I got this same error a few moments ago. I solved it deleting the "#, fuzzy" tag over the translation strings in my django.po files. It seems that translated text is not served if it got this tag, so make sure to translate the text and then delete this line.

Here is an example of a translated text not server on a po file:

     #: course/models.py:13
     #, fuzzy
     msgid "code"
     msgstr "código"

So, just delete the flag and leave it like this:

     #: course/models.py:13
     msgid "code"
     msgstr "código"

I hope this work for you. Good luck!

Reference: http://share-experiences.com/blog/what-fuzzy-means-python-django-gettext/

PD: I know you got this issue a few month ago, but I leave this response due that you we never heard if you got this problem solved.

12
votes

Had a same/similar issue with translations not showing up. Setting the LOCALE_PATHS fixed the issue:

# settings.py
USE_I18N = True
USE_L10N = True

LOCALE_PATHS = (
  '/path/to/djangoapp/locale',
)
7
votes

Translation files (PO) are loaded in memory only one time, changes to the PO files are not picked up by Django. In order to load the new translation files you need to restart Django (eg. stop/start runserver, Apache or NGINX).

1
votes

One additional reason for Django translations not working is to compile the .po file with a Python version different than the one being used to run your application. Make sure you use the same version.

0
votes

Make sure to use ugettext_lazy and not ugettext

0
votes

If you are using gettext.translation to get the translations, i.e:

text_de = gettext.translation('django', locale_dir, ['de'], fallback=True).ugettext('Welcome to my site')

... and your translation works on the development server but not on production, note that locale_dir must point to your locale directory. It might be located elsewhere on one of the systems. Spent like 2 hrs finding it.

-2
votes

Check for the USE_I18N setting. More info. Anyway, I think by default it's True...