feat(#16): raise error when fuzzy detected

[angryfoxx]

No description provided.

[flashcode]

Hello @angryfoxx,

Thanks for your PR!

Fuzzy strings are not really "errors" in the file, as they are not used at runtime (it's like if strings were not translated).

But I agree it's nice to know we have fuzzy strings in the translations.

By the way you have some other easy ways to find them, for example with msgfmt:

$ msgfmt --statistics --output-file=/dev/null de.po
3849 translated messages, 4 fuzzy translations.

Or with pocount:

$ pocount de.po
Processing file : de.po
Type               Strings      Words (source)    Words (translation)
Translated:    3849 ( 99%)      37112 ( 99%)           40811
Fuzzy:            4 (  0%)         18 (  0%)             n/a
Untranslated:     0 (  0%)          0 (  0%)             n/a
Total:         3853             37130                  40811

Unreviewed:    3849 ( 99%)      37112 ( 99%)           40811
Needs-Work:       4 (  0%)         18 (  0%)               0

It could be added in msgcheck as well, but this should be an optional check disabled by default (with a new command line option), as msgcheck is really focused on "errors" in translations, ie typos, punctuation, etc., not on translation progress (number of fuzzy or untranslated strings).

[angryfoxx]

ok i will work on this, i think this tool would be great after this implemantation thx for your review @flashcode