makemessages shouldn't translate applications already translated

[Marc Garcia]

When creating a django project, that I want to translate at project level (not application by application). Then, in my project I want to add a reusable/external application that is already translated (for example django-registration). The result is that in my project .po file I have all strings that are already translated in the external application.

I think that it should be avoided, and could be easily achieved by omitting applications with a locale directory.

Also if I want to copy django inside the project (that could be useful for version specific/patched installations), all django strings are included in my django.po file.

[Marc Garcia]

It could be better to make it language specific. So imagine that an application is translated in language A, but not B, but our project is translated to A and B. Then we should include all literals from that application in .po file for language B, but no A.

Attaching new patch for it.

[Marc Garcia]

Patch that fixes problem in a language specific way.

[Ramiro Morales]

Duplicate of #7050. There, Malcolm also describes another related possible requirement to handle this multiple-app scenario in a consistent way.

[Jacob]

Milestone 1.0 deleted