babel.cfg deprecation ?

[sveetch]

I don't find anymore documentation about this file which was the reference config a long time ago and so i'm unable to find the right location for it in project templates (at root ? in project ? ... ?).

And is it still really implemented ? Maybe it have moved to another file ?

We have to find to enhance things, for now we may assume it as broken, however not any error is raised with Jinja and PO/MO files, but it may be with using the po CLI (didn't tested it again yet).

So finally what we will do:

• [x] The Optimus Bootstrap template will remove the config file and expose the proper settings instead of the default one from Optimus that are base for the 1.x.x era project structure;
• [ ] The documentation have to be updated to say the config file is needed for using Babel directly;
• [ ] The default settings have to be updated to fit the new default project structure (even the starter use something like the bootstrap template);
• [ ] Documentation for settings have to be clear about the relation with the project structure;
• [ ] Translation from code have to be explained in documentation (need to use {{ gettext(VARIABLE) }});

[sveetch]

The babel.cfg file is indeed not commonly used since we define this config directly on babel.messages.extract.extract_from_dir from settings I18N_EXTRACT_MAP and I18N_EXTRACT_OPTIONS.

However the babel.cfg file may be used when user try to manage translation himself directly from Babel cli, this is documented in Optimus doc: https://optimus.readthedocs.io/en/latest/i18n.html#managing-translation-catalog-with-the-raw-way (this part is not up to date with Babel last release).

Additionally during my researches i found that string in code defined with gettext() are not translated in template render.

So with the following view code:

from gettext import gettext as _
from optimus.pages.views import PageTemplateView

class GenericPageView(PageTemplateView):
    """
    Basic page view.
    """
    title = "Not used"
    template_name = "generic.html"
    destination = "{language_code}/index.html"

    def get_title(self):
        return _("Generic basic page")

And this template:

<div>
    <h2 class="variable">{{ page_title }}</h2>
    <h2 class="hardcoded">{% trans %}Generic basic page{% endtrans %}</h2>
    <p>{% trans %}Hello World!{% endtrans %}</p>
</div>

The texts in tags {% trans %} are correctly translated, it demonstrates language and proper translations are given to Jinja. However the {{ page_title }} that is a gettext variable is still in english. The variable does not seem to be possibly rendered during. So for now, translated string can only work a translatable string in template, not from code (views or settings).

[sveetch]

Ok so finally the variable work but you must not just define it as a variable in template like this in template:

{{ page_title }}

But you need to define it in template like this:

{{ gettext(page_title) }}

So it just need to be documentated.