django-modeltranslation-wrapper 1.2.2

Autodiscover

This app changes the way that the translation files are sought for. In MT, you have just one file per project. Wrapper makes it more like in the admin: every application in INSTALLED_APPS is examined and its translation.py is imported (if present).

Moreover, if you still want to include some non-app translations (e.g. translation for 3rd-party apps), there is new setting introduced: MODELTRANSLATION_TRANSLATION_FILES. It should contain list of additional modules (containing translations) to import.

So, when using Wrapper, the MODELTRANSLATION_TRANSLATION_REGISTRY setting is unnecessary.

For backward compatibility with MT, when MODELTRANSLATION_TRANSLATION_REGISTRY is present, it is treated as if it was listed in MODELTRANSLATION_TRANSLATION_FILES. So no changes are required in existing projects using MT.

Intelligent manager

Wrapper changes managers in translatable models so that they are aware of active language in their operations. That means, unsuffixed attributes parameters are rewritten to the suffixed versions.

These statements give the same results, assuming current active language is pl:

X.objects.filter(foo='bar')
X.objects.filter(foo_pl='bar')

activate('de')
X.objects.filter(foo_pl='bar')  # Still the same result

If the translatable model has own custom manager, intelligent manager will be gently added, retaining old functions.

The X.objects.create() is special case, however. For backward compatibility it works as in MT by default. But you can pass parameter _populate=True to populate suffixed fields with values from unsuffixed ones.

Example will clarify it:

x = X.objects.create(foo='bar', _populate=True)

is equivalent of:

x = X.objects.create(foo_en='bar', foo_pl='bar', ... , foo_zu='bar')

or:

x = X.objects.create(foo='bar')
x.foo_en = 'bar'
x.foo_pl = 'bar'
...
x.foo_zu = 'bar'
x.save()

Moreover, some field can be explicitly assigned different value:

x = X.objects.create(foo='-- no translation yet --', foo_pl='nic', _populate=True)

It will result in foo_pl == 'nic' and other foo_?? == '-- no translation yet --'.

There is more convenient way than passing _populate all the time: MODELTRANSLATION_AUTO_POPULATE setting. If _populate parameter is missing, create() will look at the setting to determine if population should be used.

This useful feature is disabled by default for backward compatibility with MT tests. However, if your code doesn’t heavily rely on the fact that create() set None on suffixed fields, it is advised to set MODELTRANSLATION_AUTO_POPULATE = True.

New settings

MODELTRANSLATION_TRANSLATION_FILES

Default: ()

List of additional translation modules to import.

MODELTRANSLATION_AUTO_POPULATE

Default: False

This setting control if X.objects.create() function should populate language fields values.