Re: [Django] #6376: Allow using custom gettext domains
Django
-------------------------------------+-------------------------------------
Reporter: dennis@… | Owner: Rui
| Pereira
Type: New feature | Status: assigned
Component: | Version: master
Internationalization |
Severity: Normal | Resolution:
Keywords: gettext | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Rui Pereira):
* needs_better_patch: 1 => 0
--
Ticket URL: <https://code.djangoproject.com/ticket/6376#comment:22>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
-------------------------------------+-------------------------------------
Reporter: dennis@… | Owner: Rui
| Pereira
Type: New feature | Status: assigned
Component: | Version: master
Internationalization |
Severity: Normal | Resolution:
Keywords: gettext | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
* needs_better_patch: 0 => 1
Comment:
Current patch:
* Allows finding translations from `LOCALE_PATHS` but not
`INSTALLED_APPS`.
* Doesn't allow working with `makemessages`.
Not sure it meets the criteria outlined above:
> Application authors must be able to create PO files in their
applications and users of those applications must be able to use them
Maybe it would still be good enough to allow the ''external translations''
#20070 talks about, so perhaps we could take it as it is on that basis.
([https://github.com/django/django/pull/10687#pullrequestreview-257327462
Discussion on PR].)
If so, documentation changes need some improvement.
--
Ticket URL: <https://code.djangoproject.com/ticket/6376#comment:23>
Django
-------------------------------------+-------------------------------------
Reporter: dennis@… | Owner: Rui
| Pereira
Type: New feature | Status: assigned
Severity: Normal | Resolution:
Keywords: gettext | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
The Creative Common (CC) legal tools (636 licenses and 3 public domain
tools) require multiple distinct translation domains so that we can have
different workflows for legal text (high friction/gatekeeping) and non
legal text (low friction/gatekeeping):
We have a functional workaround ([https://github.com/creativecommons/cc-
legal-tools-
app/blob/2e13c4085cd90d2cc340611fd09ce3e080c347e5/i18n/utils.py#L67-L138
i18n/utils.py#L67-L138]) but it manipulates the private `_active`
variable, which seems fragile to me.** Proper support for being able to
specify a translation domain would very helpful.**
Related repositories:
- [https://github.com/creativecommons/cc-legal-tools-app/ creativecommons
/cc-legal-tools-app]: Legal tool (licenses, public domain dedication,
etc.) management application for Creative Commons
- [https://github.com/creativecommons/cc-legal-tools-data creativecommons
/cc-legal-tools-data]: Legal tool (licenses, public domain dedication,
etc.) data for Creative Commons
--
Ticket URL: <https://code.djangoproject.com/ticket/6376#comment:24>