Django/django
11
0
Fork 0
Code Pull Requests Projects Releases Activity

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

Browse Source 
Backport of 3d664a158de18acf72fc8e0671f0f390cbca4b2e from master
This commit is contained in:
sebashwa 2020-06-12 15:29:13 +02:00 committed by Mariusz Felisiak
parent e2cdbc585a
commit 33767d5ab6
2 changed files with 10 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/ref/django-admin.txt
View File

@ -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

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

@ -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::