opendev/infra-manual
Code Issues Proposed changes

translation: drop babel extractor definitions

Browse Source 
babel extractors are now registered via python entry points,
so there is no need to declare babel extractors in babel configs.

This allows us to switch the message extractor easily.
For example, the horizon team plans to switch the babel extractor
from django-babel to enmerkar (a fork of django-babel) near future
as django-babel does not work with Django 2.2 (the recent LTS of Django)
and looks unmaintained for over two years.

Change-Id: I4580aa4b0f1ba2f6fd4dcaa3510b665ca5a77024
This commit is contained in:
Akihiro Motoki 2019-12-27 01:39:04 +09:00
parent 9bd44458ba
commit f0627aeff7
1 changed files with 0 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
doc/source/creators.rst
View File

@ -1224,9 +1224,6 @@ Create file ``babel-django.cfg`` with the following content:
.. code-block:: ini
[extractors]
django = django_babel.extract:extract_django
[python: **.py]
[django: **/templates/**.html]
[django: **/templates/**.csv]
@ -1235,19 +1232,7 @@ Create file ``babel-djangojs.cfg`` with the following content:
.. code-block:: ini
[extractors]
# We use a custom extractor to find translatable strings in AngularJS
# templates. The extractor is included in horizon.utils for now.
# See http://babel.pocoo.org/docs/messages/#referencing-extraction-methods 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]
ReactJS Projects