innov
/
django1
1
0
Fork 0
Code Issues Pull Requests 1 Projects Releases Wiki Activity

Fixed #31690 -- Added note about fuzzy entries in translation docs.

This commit is contained in:
sebashwa 2020-06-12 15:29:13 +02:00 committed by Mariusz Felisiak
parent 6b25d24a57
commit 3d664a158d
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

@ -160,7 +160,7 @@ are excluded.
.. django-admin-option:: --use-fuzzy, -f
Includes fuzzy translations into compiled files.
Includes `fuzzy translations`_ into compiled files.
Example usage::
@ -173,6 +173,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
Ignores directories matching the given :mod:`glob`-style pattern. Use

7
docs/topics/i18n/translation.txt
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
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::