Hi, I think the setting is worth it, it can be really useful when working with complex translation setups.
However, I feel that LOCALE_FILENAMES is a poor choice for the setting name, as it differs from standard gettext terminology in a very unclear way. Why not name it LOCALE_DOMAINS? (To me, _FILENAMES sounds as if I should pass either a path or at least a full filename, but it is neither of both.) Raphael Am Tue, 28 Jul 2015 11:48:14 -0700 (PDT) schrieb Tim Graham <timogra...@gmail.com>: > Since adding new settings is sometimes controversial, I wanted to ask > for thoughts about this ticket [1] / pull request [2] which proposes > a new LOCALE_FILENAMES setting to allow using additional gettext > domains besides "django". I don't use translations myself, so > thoughts about whether the usefulness of the feature justifies a new > setting or if there is some other solution to the problem described > in the ticket would be welcome. > > [1] https://code.djangoproject.com/ticket/6376 > [2] https://github.com/django/django/pull/5053 > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/20150820153900.300d77ec%40kvothe. For more options, visit https://groups.google.com/d/optout.
pgpyKOcMfnmQ2.pgp
Description: Digitale Signatur von OpenPGP
