When there are more than one occurrence of a term in the source string, even there equal number of occurrences of target term in the target, I always get this QA error.
Anyone know how to get rid of this error?
I am using the latest version of Studio 2022.
My settings:
Thank you,
Truc
Can you also provide a screenshot of the offending segment and also the QA message so we see it in context?
Have you tried increasing the term repetition threshold?
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
Hi Paul,
Here is the screenshot:
Thanks for the sample. I don't really get consistent enough results to be able to prove it's exactly the problem you have found. I do think there is a problem though... for example:
I tested three scenarios:
I put my test project here if you want to check?
https://community.rws.com/cfs-file/__key/communityserver-discussions-components-files/91/occurrences.docx_5F00_en_2D00_US_5F00_vi_2D00_VN.sdlppx
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
Thanks Paul!
It's strange that when I set the term repetition threshold to 2 or less, the error is gone.
Hello all, I'm having the same issue, the setting of the repetition treshold doesn't make any difference in my case though. It is quite an annoying problem though because in large files it yields a very large amount of false "target term not used" warnings. I might be mistaken but I think the problem started with the previous update of version 2022. Any clue yet of what causes this?
Hello all, I'm having the same issue, the setting of the repetition treshold doesn't make any difference in my case though. It is quite an annoying problem though because in large files it yields a very large amount of false "target term not used" warnings. I might be mistaken but I think the problem started with the previous update of version 2022. Any clue yet of what causes this?
Translate
