On 12/30/2015 11:27 PM, Clark Boylan wrote:
The problem with using a tox target is that we use privileged Jenkins
machines to do the extraction and don't want arbitrary code to run on
them. It would be possible to run arbitrary code if we used a tox
target.
Clark, we run already
I'm currently looking into simplifying and consolidation of translation
setup for projects (draft spec at [1]) and have a question for dashboard
translations. Right now, horizon uses django.pot and djangojs.pot - and
most *-dashboard projects use the same names. Are these names enforced
by the
I haven't looked into the code detail, but as far as I read
https://docs.djangoproject.com/en/1.9/topics/i18n/translation/#specialties-of-django-translation
it is enforced by django framework.
How django searches message catalogs is described at
