summaryrefslogtreecommitdiff
path: root/docs/topics
diff options
context:
space:
mode:
authorsebashwa <sebashwa@mailbox.org>2020-06-12 15:29:13 +0200
committerMariusz Felisiak <felisiak.mariusz@gmail.com>2020-06-15 07:58:47 +0200
commit3d664a158de18acf72fc8e0671f0f390cbca4b2e (patch)
tree3fb80585937d996ddde3daf4f92d6d7abbc7b73b /docs/topics
parent6b25d24a5755bb90c037e2afd485668bae8f179e (diff)
Fixed #31690 -- Added note about fuzzy entries in translation docs.
Diffstat (limited to 'docs/topics')
-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 7afe47c149..1fa2c7e711 100644
--- a/docs/topics/i18n/translation.txt
+++ b/docs/topics/i18n/translation.txt
@@ -1619,6 +1619,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::