Browse Source

Drop babel extractor definitions from babel config

Babel allows us to register babel extractors via entry points.
This means we no longer need to have extractor definitions in
each babel config files. All horizon plugins have copies of
babel-django.cfg and babel-djangojs.cfg now. By dropping the
extractor defintiions from babel config files, we can make
a potential migration from django-babel to enmerkar (and
we can also avoid more modifications of babel config files
even if more transition is required).

django-babel and enmerkar both define 'django' extractor
in the entry point, so we can drop it from babel-django.cfg.
This commit also registers 'angular' extractor, so we can drop
the extractor for AngularJS from babel-djangojs.cfg.

Change-Id: Icf93d4551bd3db1baa84c110f06dcc1c36e18b7e
Akihiro Motoki 1 year ago
3 changed files with 5 additions and 10 deletions
  1. +0
  2. +0
  3. +5

+ 0
- 3
babel-django.cfg View File

@ -1,6 +1,3 @@
django = django_babel.extract:extract_django
[python: **.py]
[django: **/templates/**.html]
[django: **/templates/**.csv]

+ 0
- 7
babel-djangojs.cfg View File

@ -1,10 +1,3 @@
# We use a custom extractor to find translatable strings in AngularJS
# templates. The extractor is included in horizon.utils for now.
# See for
# details on how this works.
angular = horizon.utils.babel_extract_angular:extract_angular
[javascript: **.js]
# We need to look into all static folders for HTML files.

+ 5
- 0
setup.cfg View File

@ -54,3 +54,8 @@ add_comments = Translators:
oslo.config.opts =
openstack_dashboard = openstack_dashboard.utils.config:list_options
# We use a custom extractor to find translatable strings in AngularJS templates.
# See for
# details on how this works.
babel.extractors =
angular = horizon.utils.babel_extract_angular:extract_angular