We need to investigate the cause of fuzzy strings

[timlinux]

Problem

Certain strings do not appear in translated documentation outputs. It seems to relate to the presence of the 'fuzzy' gettext indicator e.g.

# 0e7f4bc362b14daf8c619b667e7700de
#: ../../source/user-docs/impact_function_docs/FloodBuildingImpactFunction.rst:26
#, fuzzy
msgid ""
"**Actions**: Provide details about where critical infrastructure might be "
"flooded"
msgstr ""
"**Actions**: Menyediakan rincian mengenai dimana area yang tergenang banjir "
"berada"

Proposed solution

• Investigate when and how strings are marked as fuzzy
• describe and document the workflow to ensure that translators and coders know how to ensure that all translations are used properly

Expected outcome

• we understand the causality of translation issues such as fuzzy
• documentation translations are as complete as the completed translation work that has been carried out.

[mach0]

As far as I understood it right now strings are still marked as "fuzzy" if they are coming from transifex not being "reviewed" ..
So transifex workflow as a "must" have is:

• translate string
• review string

and than there are no fuzzy strings any more

[emirhartato]

Most of documentations are 99% translated. It still needs to be reviewed, if you could put priority list what document that should we reviewed first, that would be helpful as usually I reviewed documents randomly :)

[mach0]

looks like fuzzy strings are no problem anymore .. might be caused by an update of sphinx ..

closing this unless the problems appear again