Comment 19 for bug 128324

One proper way to fix this bug without causing any performance problems is:
 * Whenever a new PO file is created with *some* translations, create "current" TranslationMessage for each of the translation credits messages
 * Whenever a new POTMsgSet is added, if it's one of translation credits messages, create a "current" TranslationMessage for all existing POFiles containing at least some translations
 * Write a script to update all existing POFiles with the same translation (eg. "AUTOMATED TRANSLATION")

The reasoning for the above is the following:
 * "current" translation is not shown on any of these messages
 * POFile needs to have at least some translations to get anything to fill up the message, so it will be untranslated message if PO file is empty
 * No statistics calculation or UI code would need to change for this approach to work everywhere else

I'll make sure this is fixed asap, because it's causing even bigger problems with things like dashboard (bug 455185).