Reviewing changed non-100% match segments

Question

Hi - I have the following issue, I am sure many of you have come across. 
 I am translating multiple files where some segments are 100% matches, but in other segments there are only small changes - say one or two words. 
 During tranlsation everything works fine - trados will show the similar segments and tell you what has changed. 
 However, during review this is not the case. 
 So my question is - is there a way to force Trados to show you the changes you have made in similar (not 100% identical) segments so you can implement them in other very similar segments (with one or two words or numbers changed/added)? 
 Example: 
 Translation: 
 Arius X is your ticket to riding more, and to places you never imagined possible - I translate this to the target language and confirm the segment. 
 Sirrus X is your ticket to riding more, and to places you never imagined possible - trados shows me the first segment indicating the first word has changed, I translate it and confirm the segment. 
 Review: 
 I thought of a better word in the translation to the first sentence, so I change it and and confirm the reviewed segment. 
 When I come across the second sentence I would need Trados to show me the first sentence and remind me what I have changed in the translation - unfortunatelly I have not found a way to do this. 
 When the text is short, you may remember that you have changed something and can look the sentence up using concordance. 
 However, when there are hundreds of files with hundreds of changes, there is no way to remember all. 
 Any suggestions? How do you deal with this type of sentences?

Daniel Hug · Accepted Answer

Marcel Hlbočan 
 That's a tricky one, because Trados Studio's inconsistency check is for identical segments, not for similar segments. There are a few options though. 
 Display fuzzy segments even if there is an exact match. 
 Let's assume this is my text, I am translating and in segment 5, and Trados Studio displays the TM match from segment 1 to me, because they are 96% matching. This is what you describe. 
 
 Later on, I am reviewing, I changed the translation of "ticket" in segment one. Now I am in segment 5 again: 
 
 Trados displays the context match to me, but it also displays fuzzy matches. It's an option you have to activate in project settings: 
 
 That would be the easiest and most flexible way in mid-translation, so to speak. You get segments displayed that are similar in the source language, independent of whether you altered the translation or not. 
 Other options 
 If you know ahead of your translation that you will be dealing with a variety of products that don't need to be translated, you can define the respective terms as labels. I have done so for the three ticket names here: "Arius", "Sirius" and "Betelgeuse". 
 When translating, Studio auto-propagates my translation: 
 
 And in Review mode, after I change "Ihr Ticket" into "Ihre Fahrkarte", I get this: 
 
 This is pretty cool, but the labels have to match 100%. So if you have "Sirius" once and "Sirium" somewhere else it won't work. And you have to know your labels ahead of time. 
 A very similar path is to define these words not as labels (in the TM), but as tags (at project generation): 
 
 And you get basically the same situation when you change something during review: 
 
 The main difference is that you can't change the tag in the translation (so you'd be stuck if the target language would require some inflection etc.) and it's stored in the TM differently. With the labels approach, you'd get three TM entries with this text, while with the tags approach you'd get one TM entry that knows there is a tag, but it does not know what the tag contains. You have to decide what you want. 
 Hope this helps a bit. There might be more options, but just off the top of my head, these three came to mind. 
 Daniel

Trados Studio > 1. Trados Studio

Reviewing changed non-100% match segments

Top Replies