summaryrefslogtreecommitdiff
path: root/po
diff options
context:
space:
mode:
authorLibravatar Bagas Sanjaya <bagasdotme@gmail.com>2021-05-17 19:40:38 +0700
committerLibravatar Jiang Xin <worldhello.net@gmail.com>2021-06-02 11:21:26 +0800
commit3714fbcb45dcd523ceb99610fe90b43b49a02e67 (patch)
tree368c79bf7e0920cfeca0faff8328bd87654093e8 /po
parentl10n: README: document l10n conventions (diff)
downloadtgif-3714fbcb45dcd523ceb99610fe90b43b49a02e67.tar.xz
l10n: README: note on fuzzy translations
Fuzzy translation problem can occur when updating translations. Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com> Signed-off-by: Jiang Xin <worldhello.net@gmail.com>
Diffstat (limited to 'po')
-rw-r--r--po/README.md12
1 files changed, 12 insertions, 0 deletions
diff --git a/po/README.md b/po/README.md
index f6f376eedf..2fd92cca04 100644
--- a/po/README.md
+++ b/po/README.md
@@ -159,6 +159,18 @@ in the po/ directory, where XX.po is the file you want to update.
Once you are done testing the translation (see below), commit the result
and ask the l10n coordinator to pull from you.
+Fuzzy translation
+-----------------
+
+Fuzzy translation is a translation marked by comment "fuzzy" to let you
+know that the translation is out of date because the "msgid" has been
+changed. A fuzzy translation will be ignored when compiling using "msgfmt".
+Fuzzy translation can be marked by hands, but for most cases they are
+marked automatically when running "msgmerge" to update your "XX.po" file.
+
+After fixing the corresponding translation, you must remove the "fuzzy"
+tag in the comment.
+
Testing your changes
--------------------