Hi,

what exactly you would like to achieve? Not search segments which were already translated?

Regards

Patrik

Hi,

Yes, that is what I would like to achieve.  I do not want to translate segments that Trados Studio has TM-matched with confidence.  I am not clear what Studio settings are needed for this nor what the Trados Studio plugin needs to do to avoid these segments.

Thanks,

Doug

Hi,

in upcoming release of Studio we introduce a new feature which does exactly what you want - it will be generic for all MT providers and user can select who exactly it should behave e.g. search in MT if my TM matches are lower than 70%.

Regards

Patrik

Thanks, Patrik.  Prior to the new Studio release, what do I need to do within my Trados Studio plugin to prevent translations of TM-matched segments?

As far as I know, the only way to do this is to have the user set the option in the "search" page under the project settings..."Only show translation matches from first translation source that returns matches".  

The downside is that it will only ever return one result, even if the user is using two or more TMs....so it's definitely suboptimal.

The reason is that, to my knowledge, there is no way to determine in a plugin whether another provider has returned a match and/or what that match percentage is.  You can check the ConfirmationLevel of the TranslationUnit, but I think that is generally only useful to determine the status of the segment before the user navigated into it.

So the change described above is a much welcome update...looking forward to it

As far as I know, the only way to do this is to have the user set the option in the "search" page under the project settings..."Only show translation matches from first translation source that returns matches".  

The downside is that it will only ever return one result, even if the user is using two or more TMs....so it's definitely suboptimal.

The reason is that, to my knowledge, there is no way to determine in a plugin whether another provider has returned a match and/or what that match percentage is.  You can check the ConfirmationLevel of the TranslationUnit, but I think that is generally only useful to determine the status of the segment before the user navigated into it.

So the change described above is a much welcome update...looking forward to it