django internationalization and translations problem

Question

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.

Answer 1

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?

Answer 2

After you change/create the po file(s) you need to compile those files. Something like:

django-admin.py compilemessages

Go to 'Compile Message Files' here for more info.

Answer 3

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

Answer 4

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.

Answer 5

You always have to restart the web server in order to use the new po compiled files (even if you're using the runserver thing)

Answer 6

For this problem i recommend you use django-rosseta :http://code.google.com/p/django-rosetta/ automatically compile the messages when you save a translation.