Admin application doesn't get translated when using Apache + mod_python

[Hilbert Schraal <hilbert@…>]

I'm deploying django 0.96.1 on Apache + mod_python on debian etch. In
the setting.py I have:

LANGUAGES = (

('nl', 'Dutch'),

)

LANGUAGE_CODE = 'nl'

USE_I18N = True

On development using 'manage.py runserver' I have the admin app
translated in Dutch. Behind Apache + mod_python the admin app always
shows up in English. I even have set my language preference in my
browser to Dutch, to no avail.

I'm attaching my settings.py and my Apache2 config for reference.

[Hilbert Schraal <hilbert@…>]

This site serves the media and redirects to mod_python for dynamic content

[Hilbert Schraal <hilbert@…>]

This sites serves the dynamic content using mod_python

[mrts]

I can confirm that this does not work in 0.96.

But it works properly in nf-admin, so marking nf-admin-fixed.

[Hilbert Schraal <hilbert@…>]

Good te hear it is fixed in a branch, but how do I solve this issue for the stable release? Is the patch going to be backported to 0.96? For us it is not really an option to switch to an unstable branch.

[James Bennett]

Fixes are typically only backported to old releases when they involve critical security vulnerabilities. If your policy is only to run on a packaged release of Django, you will need to wait until the next release occurs, which cannot be predicted in advance.

[Malcolm Tredinnick]

Confirmed that this works correctly with mod_python and trunk. Closing, since the 0.96.1 release is just 0.96 plus security fixes and 0.96 is a snapshot of a point in time, so it won't ever be re-released.

[Hilbert Schraal <hilbert@…>]

Is there a workaround for this problem? Except of copying all admin templates and do the translation in the copies?

[Malcolm Tredinnick]

Since we don't actually know what the problem was that was fixed to change the behaviour between 0.96 and trunk, it's difficult to suggest a workaround. Try doing a scan through all closed tickets in the internationalization component and see if any of them look like possibilities.

Alternatively, you could check out trunk and bisect the changesets until you find the one that makes it worse. There have been less than 3000 commits between 0.96 and now on trunk, which means it will take at most 21 attempts to find the commit that fixed the problem.

[Malcolm Tredinnick]

*sigh* Bad moment for a typo... when I wrote "21" above, I meant "12". :-(