What's new in Python {{ version }}?

{% trans %}What's new in Python {{ version }}?{% endtrans %}

The Python Documentation

is easy to parse, extract the sentence, translate it, and, at compile-time, search and replace the sentence by its translation, nice. Here are more details about it. Would be hard to parse: we'll need to introduce an heuristic to tell if we keep the HTML tag in the translation, or split it in three sentences "Here are", "more details", "about it". Sadly, splitting it in three sentences is not possible, because in some languages the order or those blocks may be swapped. So we need to get the and inside the sentence to allow translator to move the three part around freely. Also, the Jinja xgettext parser handle variables inside translation, to start from a non-standard syntax ``{{ variable_name }}`` to a more standard one (normally ``%s`` so the string can be used on almost every languages, but here) ``%(variable)s``. Those variables are obligatory, without them we'll get *code* inside translations strings, like ``pathto("whatsnew/index")``, which is even uglier than ``%(variable)s``. Here it is: {% trans whatsnew_index=pathto("whatsnew/index") %}or all "What's new" documents since 2.0{% endtrans %}

Which yiels, in po files: "or <a href=\"%(whatsnew_index)s\">all \"What's new\" documents since 2.0" Which is better than: "or <a href=\"{{ pathto("whatsnew/index") }}\">all \"What's new\" documents since 2.0" Which itself is better (for the re-ordering problem in other languages) than: "or" "all \"What's new documents" "since 2.0"