Users trying to continue a translation may found that some of the paragraphs are misplaced when the translation is loaded without an apparent reason, generating confusion. This is produced because the source article changed and they no longer match the paragraphs stored in the translation.
Trying to use the updated source is useful for the user to consider the latest content, but for the cases where the content cannot be mapped it would be preferred to fallback to the original version of the article that was used when the initial translation was started.
That is, if CX cannot map all the paragraphs when restoring a translation, load the article revision that was available when the translation was started.
Considered design goals:
- Don't force a choice. Most of the time users will be interested in completing their translation and publishing it.
- Inform the user about the issue. We want to let the user know the article changed to avoid the user to have to check or to get surprises after publishing it.
- Inform of the possible paths forward. It is totally ok to just continue the translation, but users can consider starting it again if that is what they want.
- When it is not possible to map the translated content with the translation, load the original version automatically.
- Show a warning: "This translation is based on an older version of the content. The source page may have changed significantly. You can continue this translation or start it again to use the updated content."
- (If it is easy to implement) Make the "may have changed significantly" part of the message a link to the diff that compares the loaded revision with the current one, so that users can get an idea of what changed.
This is illustrated below: