Hi Pavel,

If the Russian content has to remain in the Target document then all you need to do is leave the Source segment untranslated. They will not be saved to your TM if you leave them untranslated. Lock these segments.

Both untranslated and draft status will prevent the segment from being added to your TM. If the job is going to be handled by someone else such as a project manager after delivery, I always lock any TU's that should not enter the TM and/or the Target document.

Hope this helps. 

All th best,

Ali 

(edited to remove instructions on what you could do if you don't want any untranslated Russian in your final Target document)

Hello @Pavel Tsvetkov and @Alison Field 

Not confirming the text is not the best solution, as such segments may got confirmed in the process fully automatically, for example if you open for review. Better solution is to copy source to target, put the segment on "Sign-off rejected" and lock it. This way it will remain as such, regardless what you do with the file. Only if you explicitly use go and unlock such segments and change the status with for example Toolkit, it is possible that the status changes.

Not confirming the text is not the best solution, as such segments may got confirmed in the process fully automatically, for example if you open for review. Better solution is to copy source to target, put the segment on "Sign-off rejected" and lock it. This way it will remain as such, regardless what you do with the file. Only if you explicitly use go and unlock such segments and change the status with for example Toolkit, it is possible that the status changes.