Under Community Review

Locking and setting specific TUs as read only in translation memories.

Sometimes, when managing the TUs in translations memories, I've got the feedback from the client like following.

"This TU is about the regulation, therefore, it should be kept as it is and not be revised in any cases."

Therefore, the manager should have keep the TU as it is. However, unfortunately, the mistake can be always happen and following situations would be some examples.

Case1

The reviewer in client's side sent feedback for the TU and asked the revision and the manager for TM applied to the TU.

Case2

The translator in our vendor pointed out the translation seems weird and should be revised. So the manager revised the TU.

in both cases, the TU should have kept as it is. But, as a human-being, all we make a mistake.

So, I thought if I could set the lock for the TU and set the TU as read-only, such a critical mistake won't be happened.

I googled and searched the way for it till now, but didn't find any clear options yet.

That's why I write this idea and hope it be forwarded to the developers.

Thanks for your time to read my idea:)

Wish all of you be healthy in this terrible days.

E-Global E-Global

  • I am afraid locking TUs in practice can raise it's own issues when changes are needed, especially if the segment was locked by somebody who's left the company, so access rights should be considered as well, it can be complicated to manage. I would suggest using a separate Clean TM verified by the editor/client to keep such segments that should not be changed. The workflow should be set up so that Translators can view the Clean TM and write only to dirty TM but not the clean TM, and only Editors car update the Clean TM.

  • in reply to Daniel Brockmann

    Thanks for the response, Brockmann:) Yes, for the regulated workflow, the way using PerfectMatch would be nice. However, for my case, the revision work would be occurred irregular. So, I thought it would be good if I could lock specific TUs in the translation memories, like the locked content in TU. :)

  • In many regulated workflows, PerfectMatch is heavily used to lock content in documents to avoid them being touched or changed. TM is not involved in such cases (as it can indeed introduce ambiguity or unwanted changes). Using PerfectMatch might be an option depending on workflows and document types.