When I set "Minimum match value" to 100% in terminology verification, I get the following error:
However, the termbase contains this exact term:
Does anyone know why this happens?
Here are the verification settings:
Be official definition: This value expresses the minimum acceptable degree of similarity between the terminology in the source segment and the matching terminology found in MultiTerm using fuzzy match search techniques. The higher the value, the more similar the terms must be.
What are these [ ]
Can I see what the actual segment looks like
Lyds
Lydia Simplicio | 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
Lydia Simplicio
>What are these []
Those are placeholders so the translator know to put Pinyin characters
> Can I see what the actual segment looks like
Here it is
I should also point out this happens on many projects (with different languages). This is just an example.
Jesse Good
Out of curiosity I see there is no space between carLife[..] and this does not match what I understood you have in your Termbase,
Can you change source segment for troubleshooting purposes and add a space so it reads CarLife [...]
Keen to hear if that makes a difference
Lyds
Lydia Simplicio | 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
Lydia Simplicio
I added a space and it gives the same results.
Support has told me they confirmed this as a bug that will be fixed in the next release.
Support has told me they confirmed this as a bug that will be fixed in the next release.
Translate
