Start a new topic

Segment comparation

I made this request sometime ago but wasn't taken into account, I just don't understand the CT results, it makes me take too much time to understand the results. Is me the only one who sees something is wrong in the way CT shows this results?

By the way, why the TM match from CT is SO low compared with the others?


1 person likes this idea

Wow, yeah, the way it looks when reviewing a project with tracked changes is great. Sadly, I never use Track Changes, so hadn't even seen this. 

Igor, would it be possible to implement something similar in the segment comparison formatting?

2 people like this

CafeTran Espresso 2019 uses the same font attribute (red, strikethrough) for:

  1. Text that's missing in the new source (see screenshots above).
  2. Text that's added to the new source.
  3. Text that's different in the new source.



Personally, I think that 2. and 3. should be marked separately. E.g. green underlined for inserted text, blue underlined for modified text.

2 people like this

>The setting 'Added text color' doesnt change this.

When reviewing a project with tracked changes, I noticed the new colour (green):


This looks great. Very clear!

It's even clearer than in Studio:


1 person likes this


1 person likes this

>The 11.0.5 small update uses the same colors for the added and deleted text in tracked segments and fuzzy matches.

It's finally there!!!


1 person likes this

I am having some issues, which I have posted about over @

>It is red in the last update. Your color settings are still from the previous update. Either reapply your current theme via the View > Themes menu or set it to red via View > Colors > No subsegment match color.

Since this setting is also saved in any Project Template, you'll have to repeat this step for all your individual PTs.


Have there been any changes regarding this topic in the last years? Can we turn off this strike-through feature? I find it illogical and confusing to strike through new terms instead of underlining them in another color and striking through only the old ones. With long sentences it takes me several minutes to understand what is new and what is different...

(19.2 KB)

Yes, I totally agree. Sadly, this is probably the main reason why I use memoQ as my daily CAT tool these days. I absolutely love CafeTran, and there is so much about it that is better than any other CAT tool. However, after seeing how clearly changes are marked in memoQ, compared to the way CT does it, I just couldn't go back. I use this feature very heavily in memoQ, and going back to CT would just slow me down too much.

memoQ even has two different ways to view the differences! I always use the second one, the new "Track Changes View".


Igor if you are reading this, I think this would be one of the coolest features to implement, and one that would make a lot of people very happy! If you changed this, I would definitely start using CT again.

PS: I actually install the latest version of CT every few months, just to check whether this has changed.

Here's the situation with 11.04:

Test document:

The quick fox jumps over the lazy dog.

The quick brown fox jumps over the lazy dog.

The quick white fox jumps over the lazy dog.

The quick brown fox jumps over the dog.

The quick brown foxes jump over the lazy dog.

Line 2: inserted 'brown'.

Line 3: changed 'brown' to 'white'.

Line 4: deleted 'lazy'.

Line 5: changed 'fox jumps' to 'foxes jump'.

Display in 11.04:

Line 2:



The inserted word 'brown' is marked as if it would have been deleted. 

The setting 'Added tex color' doesn't change this.

Line 3:


Comment: The replacement isn't marked in a unique color, which would be clearer.

Line 4:


Comment: Looks good.


Line 5: A dedicated color for changes would be good.

The current implementation requires the user to look at two places: the memory pane(s) and the target editor.

Perhaps it's possible/a good idea to have the highest FM from the memory with the highest priority inserted in the target editor automatically, and mark the differences there? I see that you have this approach implemented for Tracked Changes ...

>Perhaps it's possible/a good idea to have the highest FM from the memory with the highest priority inserted in the target editor automatically

This is already possible. You'll have to lower this value:


The meme is for justification LOL.

I agree there is a much needed improvement in the readability area of the TM matches comparison, both in the TM view and in the Auto-assembling view (F1).

I have recently a suggestion in this regard: that the characters defined in the "Do not match" setting (Preferences > Memory) should be displayed in the TM comparison: 

Login to post a comment