Hi Lucas,

Each segment in the translation has an "origin" which shows where it came from. Theoretically, you could add a custom workflow task to check the origin and flag up any files where (N)MT has been used. However, if a translator is determined enough, they can copy the source text, paste it into an MT engine and then copy/paste the MT translation into the file; there would be no indication that this had been done. Even less so if they then post-edited the translation. In this case, therefore, I think it's a matter of process/contract/trust to ensure that the translator has not used MT to translate the file.

David

Hi Lucas,

Each segment in the translation has an "origin" which shows where it came from. Theoretically, you could add a custom workflow task to check the origin and flag up any files where (N)MT has been used. However, if a translator is determined enough, they can copy the source text, paste it into an MT engine and then copy/paste the MT translation into the file; there would be no indication that this had been done. Even less so if they then post-edited the translation. In this case, therefore, I think it's a matter of process/contract/trust to ensure that the translator has not used MT to translate the file.

David

Hi David, what workflow task performs the task you are describing?

I agree that the process/contract/trust is the basis that we are operating on, but if we have additional control tools available to us through our Trados subscription then we are interested in understanding what they are and how they work.

Thanks very much!

Hi Lucas,

There's nothing "out of the box" that does this at present. You would have to use the API/SDK/Extensibility framework to create a custom task for your requirements. As I said, even then it's possible to "fool" the application.

David

Hi David, I understand that it would still be possible to 'fool' the check but if there were some standard analysis step to be added on to the workflow then we would have considered that. If adding such a step indeed requires API customization then that is not something we would pursue. As mentioned in my original post, during ELEVATE 2024 I had understood that this sort of check would be possible within the existing software functionality. 

If you can recall who was giving the presentation, I can probably ask them a quick message about it. As far as I'm aware, there's no such out-of-the-box workflow task available.

I participated in most of the day and probably heard from a dozen or so speakers so I unfortunately don't remember at what point this came up except that it was in response to an audience question not a part of the prepared presentations.