Comment 5 for bug 1773174

Timo, I appreciate your concerns and mostly agree with what you're saying, with some "but"s.

We are running a test across all locales. We had an issue (that was made obvious by this bug), where we weren't pulling the updated translations from launchpad back into our tree. We've fixed this, although we need to revisit to make sure it's happening automatically at some point.

The warning as presented is not actionable by users. I need to reword it so that it's clear that the expected action _is_ to file a bug (or contact us on IRC, or the snapcraft forum). I'll get on that later this week (and while this is part of addressing the root cause of this bug, I don't feel it's part of this bug per se).

Translators won't see the errors -- yeah, I don't know how to fix this. There's no simple way for a translator to update their system with the translations they just did, to see how they look in context. We have gone through all i18n'ed strings and made sure they have an appropriate // TRANSLATORS comment to mitigate this issue.

HTH, HAND.