Browse Source

translation: drop babel extractor definitions

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: Ibe6b0936d7b96d4e21217a6d0046e842cd54e789
Akihiro Motoki 1 year ago
2 changed files with 1 additions and 16 deletions
  1. +0
  2. +1

+ 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]

+ 1
- 13
babel-djangojs.cfg View File

@ -1,14 +1,2 @@
# 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.
# The **/static ensures that we also search within
# .../dashboards/XYZ/static which will ensure
# that plugins are also translated.
[angular: **/static/**.html]
[angular: **/static/**.html]