babel extractors are now registered via python entry points,
so there is no need to declare babel extractors in babel configs.
This change is important to make translation work in Django 2.2.
django-babel does not work with Django 2.2 and looks unmaintained
for over two years. The horizon team is thinking to switch the extractor
to enmerkar (a fork of django-babel) to make extraction of translation
string work again near future. It is important to drop the extractor
definition to make the transition smooth.
Change-Id: Id90a29feed0bae697168492ac43961535178fe85
Also mark some strings translatable.
This commit violates hard string freeze after RC1 phase,
but this change only add new strings and allows translators
to translate strings which cannot be tranlated now.
Change-Id: Ia3b3889347c6ccb97488409f8409cb44d6a2586f
Closes-Bug: #1561203
Follow new infra setup for translations, see spec
http://specs.openstack.org/openstack-infra/infra-specs/specs/translation_setup.html
for full details.
Prepare babel-django.cfg qnd remove babel.cfg.
This repository is django related. So, follow Django repos convention in OpenStack.
This basically renames
designate-dashboard/locale/designate-dashboard.pot to
designatedashboard/locale/django.pot to follow Django POT file convention.
setup.cfg babel entries are kept as this repository has
only python files and it still works, they have been updated for new
setup.
Change-Id: I388c6b92b9e9d7a0c9d7b81b4c495a65088e4856
Akihiro Motoki