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
Just to add to my above message, it isn't just that the TM is disabled for the translator, but the AnyTM does not even get added to the Package.
Can anyone confirm this behaviour? Is it by design?
Thanks,
Gemma
I can confirm this behaviour. Unfortunately, it has always been like this. I really hope that AnyTM project TMs will be able to be included in the project packages in a future release.
Cheers,
Annemieke
Thanks for confirming Annemieke. Hopefully it will be fixed soon.
Thanks,
Gemma
Been logged as LG-15888 if you want to chase through support or refer to it again. Been an issue for a long time!!
Paul Filkin | RWS
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. I'll keep a note of that. (Oops that I never noticed this issue until just a few months back!)
I just ran a test with a package created with Studio 2017 and opened it in 2019 SR2: the AnyTM is present and fully functional.
Hi Bart,
thanks for letting us know that this seems to be fixed :-) I had not tried it for some time...
Angelika
Hi Bart,
thanks for letting us know that this seems to be fixed :-) I had not tried it for some time...
Angelika
Translate
