Can this inconsistency be explained?
The term "Kontraktänderungsformular" appears 3x always with the same translation "contract change form" (also present in the TB).
The term is flagged once as "mismatch" - why?
Are you using multiple termbases?
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Yes, but in the past the second TB was not processed correctly.
I don’t understand your comment... but the reason I asked is that only the default termbase will be used for verification.
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
This is what I meant by "not processed correctly". Is there some "deep" reason why only the default TB is used?
The flagged term is in the first TB, but what I do not understand is why matched correctly 2x and incorrectly 1x, where the segment structure is almost identical.
Is there some "deep" reason why only the default TB is used?
Yes. It's deep in the way MultiTerm was implemented and prevents all kinds of things from being achieved, like being able to add terms to a different termbase to the default, or add terms to multiple termbases at the same time.
The flagged term is in the first TB, but what I do not understand is why matched correctly 2x and incorrectly 1x, where the segment structure is almost identical.
I can't see this in your screenshot. Only one segment seems to be confirmed so perhaps the check is only applied to one segment?
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
All segments are confirmed. I even restarted Studio after installing the update.
With regard to multiple TBs, I only want to reference them, not add anything, where I can certainly appreciate there could be problems.
To come back to your question, as I'm not even sure what we are discussing any more.
The term is flagged once as "mismatch" - why?
Possibly because the recognition is coming from a termbase that is not the default.
If it is the default then I'm afraid I don't know... perhaps try removing all termbases apart from the one default and see if this makes any difference?
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
I removed the second TB - no change.
Did you refresh the project? So close the file, select and activate another project, then go back to the original.
Paul Filkin | RWS Group
________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Translate
