From c3437f734d03d93f798151f712064394652cabed Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Wed, 18 Apr 2018 08:29:21 -0400 Subject: [PATCH] Fixed #29174, #29175 -- Doc'd that f-strings and JavaScript template strings can't be translated. --- docs/topics/i18n/translation.txt | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/topics/i18n/translation.txt b/docs/topics/i18n/translation.txt index cfd84480b8..5ef7c3db2e 100644 --- a/docs/topics/i18n/translation.txt +++ b/docs/topics/i18n/translation.txt @@ -138,6 +138,13 @@ instead of positional interpolation (e.g., ``%s`` or ``%d``) whenever you have more than a single parameter. If you used positional interpolation, translations wouldn't be able to reorder placeholder text. +Since string extraction is done by the ``xgettext`` command, only syntaxes +supported by ``gettext`` are supported by Django. Python f-strings_ and +`JavaScript template strings`_ are not yet supported by ``xgettext``. + +.. _f-strings: https://docs.python.org/3/reference/lexical_analysis.html#f-strings +.. _JavaScript template strings: https://savannah.gnu.org/bugs/?50920 + .. _translator-comments: Comments for translators