I've tried setting LANGUAGE_CODE = "es" or to anything other than "en" and it didn't work.
Actually, most of the spanish translation strings are simply commented out in the spanish .po catalogue. One example is the string "badges", visible in the top navigation menu:
#~ msgid "badges"
#~ msgstr "medallas"
The comment format is #~, which means the strings are ignored because they are obsolete. Why they are obsolete I don't know, but a simple fix is to run
[PROJECT_ROOT/apps/askbot/] PROJECT_ROOT/manage.py jinja2_makemessages --no-wrap -l es -e html,py,txt
That is, run that command from the askbot app subdirectory (not from PROJECT_ROOT where manage.py lives).
That will un-obsolete the es askbot strings and make them visible/translatable from rosetta.
which version of django are you using? The strings might have become obsoleted when someone used development django trunk to rebuild strings. Apparently only the new version can extract strings from js correctly, but they might have broken the python/html extractor.
Evgeny (Dec 20 '11)
I had exactly the same question on StackOverflow a while ago, it might help you http://stackoverflow.com/questions/1230315/cant-switch-language-environment-in-django .
Hello all,
I have the same problem, many of the translation pairs have become obsolete (with #~ in front) and even when I followed what @piskvorky suggested, they keep being obsolete.
Any suggestions?
Asked: Dec 19 '11
Seen: 106 times
Last updated: Apr 02
Copyright Askbot, 2010-2011. Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
