[Django] #34021: collect_translations
Django
-------------------------------------+-------------------------------------
Reporter: Mahdi | Owner: nobody
Firouzjah |
Type: New | Status: new
feature |
Component: | Version: 4.0
Internationalization | Keywords: translation
Severity: Normal | contextual-markers
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
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
[https://docs.djangoproject.com/en/4.1/topics/i18n/translation
/#contextual-markers 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.
--
Ticket URL: <https://code.djangoproject.com/ticket/34021>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
-------------------------------------+-------------------------------------
Reporter: Mahdi Firouzjah | Owner: nobody
Type: New feature | Status: closed
Component: | Version: 4.0
Internationalization |
Severity: Normal | Resolution: invalid
Keywords: translation | Triage Stage:
contextual-markers | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
* status: new => closed
* resolution: => invalid
Comment:
Replying to [ticket:34021 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
[https://docs.djangoproject.com/en/stable/topics/i18n/translation/#how-
django-discovers-translations docs]. I don't think any new feature is
needed. Please try to use one of
[https://code.djangoproject.com/wiki/TicketClosingReasons/UseSupportChannels
support channels] where folks should help with debugging your issue.
--
Ticket URL: <https://code.djangoproject.com/ticket/34021#comment:1>