#34021: collect_translations
-------------------------------------+-------------------------------------
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
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* 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>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018353db3fa5-fa0a2a0a-0c1f-4ddf-a854-24777d732450-000000%40eu-central-1.amazonses.com.
