summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTim Graham <timograham@gmail.com>2018-04-18 08:29:21 -0400
committerCarlton Gibson <carlton.gibson@noumenal.es>2018-04-18 14:35:16 +0200
commit8b4798c8d31b3cd9faab4caf11fca000b07f0181 (patch)
tree74cf7ccb4b56b9f041658109b7eabf8d6f9daa32
parent800778f7ad64a04401034f6b1005ec8071efc3bf (diff)
downloaddjango-8b4798c8d31b3cd9faab4caf11fca000b07f0181.tar.gz
[1.11.x] Fixed #29174, #29175 -- Doc'd that f-strings and JavaScript template strings can't be translated.
Backport of c3437f734d03d93f798151f712064394652cabed from master
-rw-r--r--docs/topics/i18n/translation.txt7
1 files changed, 7 insertions, 0 deletions
diff --git a/docs/topics/i18n/translation.txt b/docs/topics/i18n/translation.txt
index 158bc6fb58..a9fc247d0f 100644
--- a/docs/topics/i18n/translation.txt
+++ b/docs/topics/i18n/translation.txt
@@ -137,6 +137,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