100% match: segment in document and TM are identical, no further conditions

Context match: segment in document and TM are identical, the document structure level matches, the previous segment in source is the same and has the same translation as in previous document

Perfect Match: segment in document and TM are identical, surrounding segments in source and target are identical (before and behind afaik), document structure matches

Firstly, thanks for your efforts and time.

Your comment is brief and kind but not clear.

100% match is too easy, so does not needed any more wordings.
Others, two matches, you have introduced "structure" and "previous" or "surrounding" concepts but, there is no such thing in my hand.
In short, I have a single separated sentence(or segment) in a document and a single separated sentence(or segment) in a TM, that is all. 

Looking good
I'll try it out

Thanks again.

I have tested it.
But, nothing reasonable happened.

I have made a simple project using a docx and a fresh TM(no TUs within it).
And, I have finished translation, so, the TM is filled with the document's segments.

Now

I have made a simple project again using the same docx and the same TM (of course, it filled with TUs from the "previous" docx structure).
So, How's your idea ? It should displayed "PerfectMatch" all of them, right ?

Why is that ?
I guessed "100% Match" and You guessed "PerfectMatch" but, it shows "ContextMatch"es only.

attaching docx file showed at the first screenshot
TestingMSWord.zip
 

Let me test it for you and post the results here later on, when I have time.

sure
I understand that You do not have any kind of duty here.
I just say thanks again.

Enjoy

Kelly Edward

Your results are entirely as expected.  Perfect Match doesn't work that way and it's a feature only available to users with a Professional licence.  The way it works is that you would compare your file with a previously translated document in addition to your TM (although a TM is not necessary).  The main usecase for it has always been the "mid-project update" and the "leverage from a single bilingual document". It aligns the currently translated document's segments with those of the leveraged file, then recycles (copies) non-modified blocks of bilingual material into the new file, finally locking the recycled blocks and so preventing them from modification (optionally).  PerfectMatch does not disambiguate exact matches but reduces the scope of the translation (and subsequent review) to the difference between the current document and its previous version.

in this time with Excel

it shows at least once "100% Match" 

this is made following procedure:

I have made a simple project using a docx and a fresh TM(no TUs within it).
And, I have finished translation, so, the TM is filled with the document's segments.

Now

I have made a simple project again using the same contents Excel file and the same TM (of course, it filled with TUs from the "previous" docx structure).
Like this..

Kelly Edward

Kelly Edward said:

it shows at least once "100% Match" 

As expected.  Your segment #1 wasn't in your TM so a CM wasn't possible, therefore you get a 100% match.

no

at that time, the TM has perfect information within it from the first docx project..

It should be "100% Match" all of them

OR

It should be "CM" all of them (just like 2nd docx project)

But

It has "100% Match" once. Quite strange.

Not strange at all.  Your DOCX project did not have a segment with the text Sheet1.  So it should be exactly as you have shown.  One no match, one 100% and the rest CM.

no

your explanation makes thing more difficult to understand

I assume, MSExcle('s cell) is different from MSWord('s sentence), at least within Trados' inner processing, right ?
Then it should showed "100% Match" all of them. They are just same contents. Period.

But

One "100% Match" and the rest are "CM" ?...
Inconsistent.

no

your explanation makes thing more difficult to understand

I assume, MSExcle('s cell) is different from MSWord('s sentence), at least within Trados' inner processing, right ?
Then it should showed "100% Match" all of them. They are just same contents. Period.

But

One "100% Match" and the rest are "CM" ?...
Inconsistent.

you see it with your own eyes

DSI section says "P" in the 2nd docx project screenshot, means "Paragraph"
DSI section says "C+" in the 1st xlsx project screenshot, means "Cell (and etc)"

different means different, at xlsx project, displaying "CM" is absolutely wrong (...I mean, I do not understand it at all).

Kelly Edward

ok... probably I'm not explaining this well enough for you.  First of all you translated five sentences in a DOCX.  So if you now pre-translate that DOCX you can expect five CM matches.  I expect that part is clear?

Then you translated an Excel with six segments because you extracted the worksheet name from the excel.  This means your TM will be silent when looking for a translation of the first segment... this one:

It also means that when you come to the second segment, which is in your TM you will get a 100% match.  It won't be a CM match because when you translated this same segment in the DOCX it was the first sentence in the file.  In other words the context is different.

When you come to the third sentence the previous sentence was also in your TM so you get a 100% match, and the same as the rest.

I wonder if the part you don't understand is that a TM entry holds the context for it's translation.  So if you take your DOCX as an example this is what will be held for each entry:

segment #1 - stores the translation and also the fact it was the first segment in the file when it was translated.

segment #2 - stores the translation and also the fact segment #1 was translated immediately before it.

That's what was meant by the context.  You might also find this article explains better - https://multifarious.filkin.com/2013/02/13/100percent

Kelly Edward

Perhaps this will also help...

Thanks Mr. Filkin
That's a very good video clip, quite useful to me, Appreciated !!