Translations in template vars with a macro are not picked up about django-babel

[graingert]

It looks like {% call %} is a custom template tag

[joeribekker]

It's part of Jinja, yes. I don't think it has to do with that, but rather that it does work within block tags, but not within variable tags that has additional stuff (like a macro call).

Just after posting the issue here, we got it to work by reverting to our previous mapping file used by pybabel*:

-[django: templates/**.tmpl]
+[jinja2: templates/**.tmpl]
+extensions= jinja2.ext.i18n, jinja2.ext.with_

*To make that work we also added from django.conf import settings; settings.configure() to the pybabel script or it would complain.

When upgrading, we thought these extension would be picked up from the Django 1.8 template settings, where these extension are also defined:

TEMPLATES = [
    {
        'BACKEND': 'django_jinja.backend.Jinja2',
        'OPTIONS': {
            'debug': DEBUG,
            'match_extension': '.tmpl',
            'extensions': [
                'jinja2.ext.with_',
                'jinja2.ext.i18n',
                'django_jinja.builtins.extensions.UrlsExtension',
                'django_jinja.builtins.extensions.CsrfExtension',
            ],
            ...
        }
    }
]

[graingert]

@joeribekker can you create a PR with some tests that use Jinja2 in your usecase?

[akx]

You should use Jinja's Babel extractor with Jinja-based templates, not the Django one.