Most of the recent cases are caused by a bug in the message sharing code. When a new PO file is created, a corresponding one is created in all of the sharing templates. But setTranslationCreditsToTranslated is only called on the initial new PO file, so any credit strings in the sharing templates that aren't also in the initial template will end up untranslated.
For example, if I have a template with translator-credits in precise, but the same template doesn't have it in quantal, and I create a new en_AU translation in quantal, a precise en_AU translation will be created with the translator-credits message untranslated.
Most of the recent cases are caused by a bug in the message sharing code. When a new PO file is created, a corresponding one is created in all of the sharing templates. But setTranslationC reditsToTransla ted is only called on the initial new PO file, so any credit strings in the sharing templates that aren't also in the initial template will end up untranslated.
For example, if I have a template with translator-credits in precise, but the same template doesn't have it in quantal, and I create a new en_AU translation in quantal, a precise en_AU translation will be created with the translator-credits message untranslated.