You can check if a PO file is valid with the following command:

        msgfmt -c -o /dev/null <po file>
      

The following errors were found in dozzaqueux 's PO files:

gettext: languages/dozzzaqueux.po: can't guess language
gettext: languages/lclstrconsts.it.po:13:31: invalid multibyte sequence
languages/lclstrconsts.it.po:17:31: invalid multibyte sequence
languages/lclstrconsts.it.po:29:13: invalid multibyte sequence
languages/lclstrconsts.it.po:37:52: invalid multibyte sequence
languages/lclstrconsts.it.po:431:33: invalid multibyte sequence
languages/lclstrconsts.it.po:587:122: invalid multibyte sequence
languages/lclstrconsts.it.po:607:15: invalid multibyte sequence
languages/lclstrconsts.it.po:703:37: invalid multibyte sequence
languages/lclstrconsts.it.po:942:61: invalid multibyte sequence
languages/lclstrconsts.it.po:1162:41: invalid multibyte sequence
msgfmt: found 10 fatal errors
gettext: languages/lclstrconsts.pb.po: pb not a language code
gettext: languages/lclstrconsts.pliso.po: can't guess language
gettext: languages/lclstrconsts.plwin.po: can't guess language
gettext: languages/lclstrconsts.po: can't guess language
gettext: languages/lclstrconsts.ua.po: ua not a language code
      

Please ask the translator (identified by the Last-Translator field in the PO file), the language team (identified by the Language-Team field) or debian-i18n for a fix.