Dear all,
have you experienced this as well?
A project is created with TMs via AnyTM. The packages are allowed to contain the master TM.
But when the package is opened on the translator's machine, the AnyTM TMs will be deactivated. The user will have to delete them out of the project and attach them again manually.
This somewhat defies the idea of a package for the translator.
Can you confirm that this is happening for you too? Has anyone an idea how this can be avoided?
thanks,
Angelika
I am running the latest version of Studio 2019 and this bug still seems to be present.
I.e. I add TM with different language variants to those of the project using AnyTM to my project, create a package for the translator. But when the package is opened on the translator's machine, the AnyTM TMs will be deactivated with message 'The translation provider 'AnyTM: [TMname] could not be opened and has been disabled'.
Of course, I can send the offending TM separately and then translator can then attach it manually, as a workaround, but wanted to report that it still seems to be a bug (unless I'm doing something wrong).
Cheers,
Gemma
I am running the latest version of Studio 2019 and this bug still seems to be present.
I.e. I add TM with different language variants to those of the project using AnyTM to my project, create a package for the translator. But when the package is opened on the translator's machine, the AnyTM TMs will be deactivated with message 'The translation provider 'AnyTM: [TMname] could not be opened and has been disabled'.
Of course, I can send the offending TM separately and then translator can then attach it manually, as a workaround, but wanted to report that it still seems to be a bug (unless I'm doing something wrong).
Cheers,
Gemma
Translate
