Translations in launchpad when sent back to KDE upstream cause multiple pology check-kde-tp errors

[Samir Ribić]

If you used Launchpad for translating KDE applications, with intention to send the translations to upstream at l10.kde.org, and you do it, ypu will have a lot of errors detected by KDE scripts. at
http://l10n.kde.org/check-kde-tp-results/stable/

Some errors came from fact that Launchpad modifies fields in PO file with translator names and their e-mail addresses. It often puts empty translator name. Sometimes number of translators does not match number of e-mail addresses. For example, the most of errors are like this

kdeaccessibility/kmag.po 29(#2)[msgstr]: Both name and email address of translator no. 2 are empty.
kdeaccessibility/kmag.po 29(#2)[msgstr]: Both name and email address of translator no. 5 are empty.
kdeaccessibility/kmousetool.po 31(#2)[msgstr]: Different number of translator names (11) and email addresses (12).
kdeaccessibility/kmouth.po 27(#2)[msgstr]: Both name and email address of translator no. 2 are empty.
kdeadmin/kcron.po 29(#2)[msgstr]: Both name and email address of translator no. 2 are empty.

KDE upstream checks that each contributor has valid E-mail address. Such error is not detected by msgfmt --check file.po - they use special program called pology which also checks xml mismatches.

Conclusion: after exporting from Launchpad and before sending to KDE localization coordinator, you should manually clean up translator names and their e-mail address in each affected KDE file.