Revision history  [back]

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: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.

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.

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.

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.catalogue.

The comment format is #~, which means the strings 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).

That will un-obsolete the es askbot strings and make them visible/translatable from rosetta.