• State Suggested Answer
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 432 subscribers
  • Views 1328 views
  • Users 0 members are here
Options
Related

Translation memories are disabled by default when creating packages

Luciano

Something curious has been happening with projects created by one of our project managers. When any user (him or me for example) create a package from within his projects, the package projects end up with a disabled TM by default.

This leads to translators not having access to all the translation units when performing a concordance search. If they know about it, they can simply activate the TM within the project settings. However, this is a risk for translation quality we don't want to assume.

Does anyone have an idea what could be causing this?

correction made
[edited by: Luciano at 11:51 AM (GMT 0) on 25 Mar 2022]
emoji
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents Reply Children
  • 0 in reply to Paul

    In this case the project is being created with a Trados Studio project template. When I create a project using the same template, the issue does not occurr.

    The translation memory used is saved on our file server. Within our organization, all linguists have access to it. However, when creating a package we add the file-based TM. So, our external translators also have access to a copy of the TM. However, if it is disabled by default, they may not realize they are working without TM input.

    The projects are all local projects using Trados Studio 2021 sharing single user project packages.
    emoji