Redundant states are now part of the flagging system

As of July 1st the "Intentionally blank" and "Same as source language" options are now part of the flagging system. This means you can now filter on these states and apply them in bulk. This move is also paving the way toward custom (user definable) flags, which will be available soon.

Note that redundant states are deliberately not shown in the Translate tab as they do not require translation. See Translation states explained for more information.

Filtering redundant translations

Now that these options are functionally the same as flags, you can use them to filter project views and file exports.

For backward compatibility, filtering by status=translated will include redundant translations (because they are counted as complete), but you can filter on them specifically using status=blank-translation or status=same-as-source.

Legacy edge case

Translations can only have one status at a time, so it's no longer possible to mark an item as "same as source" and additionally flag it as being in error. We identified that only about 0.2% of Loco users had previously done this, accounting for less than 100 translations in about 8 million. If you are one of those few people, you will find that any such items have lost their error state.

In future this functionality will be accommodated by user defined flags. It will be possible to define a flag that shows up as an error, but which falls back to source text, or is intentionally blank.