1
0
mirror of https://github.com/django/django.git synced 2025-03-31 03:30:46 +00:00

[3.1.x] Fixed #31690 -- Added note about fuzzy entries in translation docs.

Backport of 3d664a158de18acf72fc8e0671f0f390cbca4b2e from master
This commit is contained in:
sebashwa 2020-06-12 15:29:13 +02:00 committed by Mariusz Felisiak
parent 6f526cb203
commit 2d3b6bce28
2 changed files with 10 additions and 1 deletions

View File

@ -160,7 +160,7 @@ are excluded.
.. django-admin-option:: --use-fuzzy, -f .. django-admin-option:: --use-fuzzy, -f
Includes fuzzy translations into compiled files. Includes `fuzzy translations`_ into compiled files.
Example usage:: Example usage::
@ -173,6 +173,8 @@ Example usage::
django-admin compilemessages -x pt_BR django-admin compilemessages -x pt_BR
django-admin compilemessages -x pt_BR -x fr django-admin compilemessages -x pt_BR -x fr
.. _fuzzy translations: https://www.gnu.org/software/gettext/manual/html_node/Fuzzy-Entries.html
.. django-admin-option:: --ignore PATTERN, -i PATTERN .. django-admin-option:: --ignore PATTERN, -i PATTERN
.. versionadded:: 3.0 .. versionadded:: 3.0

View File

@ -1619,6 +1619,13 @@ otherwise, they'll be tacked together without whitespace!
files are created). This means that everybody will be using the same files are created). This means that everybody will be using the same
encoding, which is important when Django processes the PO files. encoding, which is important when Django processes the PO files.
.. admonition:: Fuzzy entries
:djadmin:`makemessages` sometimes generates translation entries marked as
fuzzy, e.g. when translations are inferred from previously translated
strings. By default, fuzzy entries are **not** processed by
:djadmin:`compilemessages`.
To reexamine all source code and templates for new translation strings and To reexamine all source code and templates for new translation strings and
update all message files for **all** languages, run this:: update all message files for **all** languages, run this::