2

What are the steps to switch to a language other than 'en'?

I've tried setting LANGUAGE_CODE = "es" or to anything other than "en" and it didn't work.

quesada's avatar
65
quesada
asked 2011-12-19 12:26:51 -0500
Evgeny's avatar
13.2k
Evgeny
updated 2011-12-19 12:38:02 -0500
edit flag offensive 0 remove flag close merge delete

Comments

add a comment see more comments

3 Answers

2

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 .

Evgeny's avatar
13.2k
Evgeny
answered 2011-12-19 12:37:35 -0500
edit flag offensive 0 remove flag delete link

Comments

add a comment see more comments
2

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.

piskvorky's avatar
350
piskvorky
answered 2011-12-20 12:56:19 -0500, updated 2011-12-20 13:11:48 -0500
edit flag offensive 0 remove flag delete link

Comments

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's avatar Evgeny (2011-12-20 13:02:27 -0500) edit

@Evgeny: our django.VERSION is (1, 3, 1, 'final', 0)

piskvorky's avatar piskvorky (2011-12-20 13:07:04 -0500) edit
add a comment see more comments
0

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?

zaf's avatar
512
zaf
answered 2012-04-02 14:36:35 -0500
edit flag offensive 0 remove flag delete link

Comments

add a comment see more comments