Under Community Review

Block the use of Automated Translation engines

It would be very helpful for Project Managers to have a checkbox in the Studio package creation wizard, which would allow them to block the possibility for the freelance translator to add an Automated Translation engine to the project, thus ensuring that the requirement of the customer to not use Automated Translation engines is kept.

Parents
  • In Memsource, they have this Disable MT option. So what ha-ha... You can easily dodge this requirement by using apps like QTranslate for example. It allows you to apply a couple of dozens of translation engines and dictionaries from Google Translate to DeepL for free. All you need is just to assign a shortcut of your choice and select a translation engine. Whatever be blocked by such checkbox, the app would override it because it works in any text editor (including Studio's Editor and Export-for-bilingual-review docx files).

Comment
  • In Memsource, they have this Disable MT option. So what ha-ha... You can easily dodge this requirement by using apps like QTranslate for example. It allows you to apply a couple of dozens of translation engines and dictionaries from Google Translate to DeepL for free. All you need is just to assign a shortcut of your choice and select a translation engine. Whatever be blocked by such checkbox, the app would override it because it works in any text editor (including Studio's Editor and Export-for-bilingual-review docx files).

Children
No Data