mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-06-16 17:09:12 +00:00
Code Issues 32 Releases Wiki Activity

[5.2.x] Fixed #35993 -- Documented gettext f-string support limitations.

Browse Source 
Thank you to Claude Paroz and Athena Wolfskämpf for the review.

Backport of 2c2f09055579cc6068cae6c6fd3135011d6df4f1 from main.
This commit is contained in:
Ahmed Nassar 2025-04-06 01:37:10 +02:00 committed by Sarah Boyce
parent 64ec347fc5
commit aa2c7659d5
1 changed files with 16 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
docs/topics/i18n/translation.txt
View File

@ -129,8 +129,22 @@ 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. In particular, Python
:py:ref:`f-strings <f-strings>` are not yet supported by ``xgettext``, and
supported by ``gettext`` are supported by Django. Python :py:ref:`f-strings
<f-strings>` cannot be used directly with ``gettext`` functions because
f-string expressions are evaluated before they reach ``gettext``. This means
``_(f"Welcome {name}")`` will not work as expected, as the variable is
substituted before translation occurs. Instead, use named-string
interpolation::
# Good
_("Welcome %(name)s") % {"name": name}
# Good
_("Welcome {name}").format(name=name)
# Bad
_(f"Welcome {name}") # f-string evaluated before translation.
JavaScript template strings need ``gettext`` 0.21+.
.. _translator-comments: