From 33767d5ab6d6642b324b180a308e62312bd6c685 Mon Sep 17 00:00:00 2001 From: sebashwa Date: Fri, 12 Jun 2020 15:29:13 +0200 Subject: [PATCH] [3.0.x] Fixed #31690 -- Added note about fuzzy entries in translation docs. Backport of 3d664a158de18acf72fc8e0671f0f390cbca4b2e from master --- docs/ref/django-admin.txt | 4 +++- docs/topics/i18n/translation.txt | 7 +++++++ 2 files changed, 10 insertions(+), 1 deletion(-) diff --git a/docs/ref/django-admin.txt b/docs/ref/django-admin.txt index b66ca5f551..2094c60ac9 100644 --- a/docs/ref/django-admin.txt +++ b/docs/ref/django-admin.txt @@ -156,7 +156,7 @@ are excluded. .. django-admin-option:: --use-fuzzy, -f -Includes fuzzy translations into compiled files. +Includes `fuzzy translations`_ into compiled files. Example usage:: @@ -169,6 +169,8 @@ Example usage:: django-admin compilemessages -x pt_BR 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 .. versionadded:: 3.0 diff --git a/docs/topics/i18n/translation.txt b/docs/topics/i18n/translation.txt index f29da625de..53f2f99205 100644 --- a/docs/topics/i18n/translation.txt +++ b/docs/topics/i18n/translation.txt @@ -1606,6 +1606,13 @@ otherwise, they'll be tacked together without whitespace! files are created). This means that everybody will be using the same 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 update all message files for **all** languages, run this::