Do not export untranslated strings for mo files
|Reported by:||nacin||Owned by:||somebody|
 ensured that only current strings are included in exports.
 also allowed untranslated strings to be included. However, this applies to mo and po files equally, when in reality a mo file should not receive untranslated strings. If you're exporting and deploying mo files from GlotPress, this can have some pretty bad consequences, namely blank translations in place of their English fallbacks.
Attached patch continues the abstraction approach in , providing context to for_export() so it may determine the default status.