collect_translations

[Mahdi Firouzjah]

according to a situation that I had some texts and words marked for translation that tey were also used in some djnago apps as well. my LOCALE_PATH was set to the root of project and all the marked strings were collected there but the ones in common with django apps were not translated according to what I provided and instead they were following django's translation.
so it seems that inorder to fix this conflict I have to use ​contextual-markers, both in python files and templates but there are so many strings and it is possible to miss some.
so I'm requesting a feature like collectstatic so to collect all the translation marked strings of all apps(django's default apps, user defined apps, third party packages, etc.) in a specified path so to have more control over what is going on.

[Mariusz Felisiak]

Replying to Mahdi Firouzjah:

according to a situation that I had some texts and words marked for translation that tey were also used in some djnago apps as well. my LOCALE_PATH was set to the root of project and all the marked strings were collected there but the ones in common with django apps were not translated according to what I provided and instead they were following django's translation.

The directories listed in LOCALE_PATHS have the highest precedence so the Django-provided base translation should not be used in your case, see ​docs. I don't think any new feature is needed. Please try to use one of support channels where folks should help with debugging your issue.