Translatable nodes with empty translatable fields never go away from sources tab

Updated: Comment #N

Problem/Motivation

This is about buggy user experience.

If you have a lot of content, you don't know every node. The goal is to use the source overview to see if something needs to be added to a translation job. Here's the problem:

When in entity translation, a content type contains translatable fields, but some instances have these fields empty, we're lost.
The overview claims these nodes are untranslated.
Trying to add them to a job results in an error message: They don't have any translatable content!

They never disappear from the list.
Also we can't check on the fly as this is a complex process... And we cannot do it with a query...

Proposed resolution

None currently.

It's a limitation we have.
Recommendation is to define content types based on the multilingual behavior. Possibly split the content into an untranslatable content type (that won't show up at all) and the translatable content to a separate content type that cleanly works.

Remaining tasks

User interface changes

API changes