Changes to empty translations

To address some common confusion surrounding empty translations, the behaviour of entering blank text as a translation has changed slightly.

Updating an existing translation with an empty string will now mark it as "untranslated" in your project.

• Any flag that was previously set on the translation will be cleared.
• A new revision will be created as with any normal translation change.
• The behaviour is consistent in both the "Manage" and "Translate" views.

Previously the "Translate" view saved empty strings as "intentionally blank" which is counter-intuitive to the way most platforms work. You can still mark translations as "intentionally blank" but only by selecting this as an option in the "Manage" screen. Furthermore, intentionally blank translations will not be shown to translators in the "Translate" view. This is more logical as the purpose of the feature is to avoid the need for them to be translated at all.

Batch flagging

Some major UI improvements recently introduced multi-select in the "Manage" view. In addition to tagging and deleting that were added last week, you can now flag multiple translations in the same way.

Note that only translations may be flagged. Untranslated assets will always have the status "untranslated".