Hi JF Delannoy ,

JF Delannoy said:

The report cannot be sorted as such.

You can sort the message list clicking on the header Message (or any other header), so you’ll have the inconsistencies grouped together:

JF Delannoy said:

As exported to Excel (or further to Excel, to Word), sorting is impossible because there are merged cells.

I don’t think it’s possible to export the message list, whether there are merged segments or not. If you can do it somehow, please let me know the way.

"Sentence was translated inconsistently - compared to segment 10."

but there is no direct way to change and propagage.

Suggestion: displaying both

and ensuring that a change will be recorded in MT and will be propagated.



With hundred of inconsistencies (because of lousy propagation), I can't handle this.

How do you ensure that the valid, unique, version of a segment in the MT propatages everywhere when you have opened the whole list of files precisely for this?

Run some function from the Translation Results pane?

Go to first occurrence and validate?

Inversely: if you inadvertently validate a wrong version, it substitutes for the good on in the MT, and there is no Undo!

Hi JF Delannoy ,

JF Delannoy said:

"Sentence was translated inconsistently - compared to segment 10."

but there is no direct way to change and propagage.

Suggestion: displaying both

To display both segments, I select the Source text in the Editor and then right click to filter by that content.

Now both (or several) segments will be filtered in Editor so I can edit them as needed.

JF Delannoy said:

How do you ensure that the valid, unique, version of a segment in the MT propatages everywhere when you have opened the whole list of files

This Auto-propagation feature doesn’t have anything to do with the translation memory (TM). It kicks in even without no TM. So the content confirmed in one segment gets auto-propagated to other segments (no TM involved, although usually the TM is updated after confirming a segment, but it’s better not to mix concepts). If there is a bug in Auto-propagation, as I think you said, I’d like to know about it. In File > Options > Editor > Auto-propagation you can decide how to auto-propagate (from the confirmed segment downwards or all segments, auto-propagate to already confirmed segments or not…).

Most of the time I use this settings:

I know that not all segments won’t be auto-propagated (only downwards, so I need to go to the first repeated segment) and already confirmed segments won’t be auto-propagated either (so I need to do something manual, basically deleting the translation of repeated segments leaving only the first one, then edit+confirm the first one to auto-propagate). Yes, it’s manual, but it works for me most of the time. If a Trados user is using these settings (by the way, the default settings) and believes that all segments are auto-propagated, he/she will get unexpected results. Other settings can be used as long you know what you are doing.

After the first round of QA has been done, I press F8 key to run Verify again until no actual errors are reported and only false positives are shown.

There are a few things I didn’t understand, so if there is still anything unclear, please let me know.

Hi JF Delannoy ,

JF Delannoy said:

"Sentence was translated inconsistently - compared to segment 10."

but there is no direct way to change and propagage.

Suggestion: displaying both

To display both segments, I select the Source text in the Editor and then right click to filter by that content.

Now both (or several) segments will be filtered in Editor so I can edit them as needed.

JF Delannoy said:

How do you ensure that the valid, unique, version of a segment in the MT propatages everywhere when you have opened the whole list of files

This Auto-propagation feature doesn’t have anything to do with the translation memory (TM). It kicks in even without no TM. So the content confirmed in one segment gets auto-propagated to other segments (no TM involved, although usually the TM is updated after confirming a segment, but it’s better not to mix concepts). If there is a bug in Auto-propagation, as I think you said, I’d like to know about it. In File > Options > Editor > Auto-propagation you can decide how to auto-propagate (from the confirmed segment downwards or all segments, auto-propagate to already confirmed segments or not…).

Most of the time I use this settings:

I know that not all segments won’t be auto-propagated (only downwards, so I need to go to the first repeated segment) and already confirmed segments won’t be auto-propagated either (so I need to do something manual, basically deleting the translation of repeated segments leaving only the first one, then edit+confirm the first one to auto-propagate). Yes, it’s manual, but it works for me most of the time. If a Trados user is using these settings (by the way, the default settings) and believes that all segments are auto-propagated, he/she will get unexpected results. Other settings can be used as long you know what you are doing.

After the first round of QA has been done, I press F8 key to run Verify again until no actual errors are reported and only false positives are shown.

There are a few things I didn’t understand, so if there is still anything unclear, please let me know.

I have this settings and... it does not propagate.


I would expect it to jump to the next candidate and prompt.     Or, if this is sure ground, adapt automatically.



In his project, I have 9 files with company names, numbers acronums mentioned repetitively in 36 occasions.
I just passed all over for fish for non-adapted occurrences and change them (Ctrl T) manually.

The Filter by Source (via right click) is a nice feature
but, as it calls the Advanded Display Filter uility, it does not work well when you open several files together


I opened several files precisely to have a group effect for all edits, via propagation.

No propagation at all.

This is after an hour and a half trying to harmonize.

JF Delannoy 

JF Delannoy said:

I have this settings and... it does not propagate.

These settings won’t propagate :

• … to already confirmed segments.
• … to segments above the confirmed segment.

Any of these instances not working for you, it 's by design.

Of course, they won’t propagate to locked segments either.

JF Delannoy said:

it calls the Advanded Display Filter uility, it does not work well when you open several files together

So far no issues for me and I open several files virtually every single day.It won’t propagate to locked segment.

Downward only: I take that into account; try to edit the topmost.
Strange limitation though.

Locked: I have no locked segments.

Confirmed: Oh yes, I have confirmed segments, since I worked on these files separately. I wanted to propagate inside each, using the validation (Ctrl Enter).
Why is there no possibility to modify those automatically or semi-automatically (jumping to them?)..


I have
many segments which are checked green, but are not uptodate.
many segments saying CM but in fact no uptodate.


Presently, I am doing Search and Replace.
That's not the idea...

Hi JF Delannoy ,

JF Delannoy said:

Confirmed: Oh yes, I have confirmed segments, since I worked on these files separately. I wanted to propagate inside each, using the validation (Ctrl Enter).
Why is there no possibility to modify those automatically or semi-automatically (jumping to them?)..

To auto-propagate to already confirmed segments, you need to tick the Auto-propagate exact matches to confirmed segments check box:

Pues, sencillo..
I would have thought this was the default setting.

JF Delannoy 

JF Delannoy said:

I would have thought this was the default setting.

Why?  If you were reviewing and needed to make a small change to just one segment that should not be auto-propagated to others you couple inadvertently change them all in error.  I think this is a better default.  If you want to change something by auto-propagation after you already confirmed every segment in the file then I think you should have to specifically make that choice.

In my experience there are only rare cases where a Source sequence would produce several possible Target sequences (based on context)
so that considering fficiency, propagading more actively is interesting.

In the present job, the source set consists of successive versions of a contract and various similar amendments,
it is logical to propagate the 100%.

But overall, it's better to be prudent.

JF Delannoy 

JF Delannoy said:

In my experience there are only rare cases where a Source sequence would produce several possible Target sequences (based on context)

I'm sure you're right, and propagation will take place by default.  But this setting we're talking about refers specifically to overwriting a segment that you have already reviewed and confirmed to your TM.  So if you did happen to come across a rare example like this when reviewing a finished translation you may not be too happy if all your other segments were changed as well.

But if you do want this then just make the change in your default template and now you'll have it for all your projects in future.