Accepted, Not Yet Planned

Setting to Not Planned, as this lives elsewhere (up or downstream) and/or can be achieved by using certain processes as the comments indicate.

Lock TUs in the TM

It would be great to be able to lock a translation unit in the TM, thus making sure that it will be auto-propagated as perfect match and always remain exactly the same.

Ulrike Michiels

  • I like the concept of the idea, but a few possible issues come to mind:

    - It makes sense if the TM is only used for a specific client and their key translations.

    - TUs marked as locked need to be findable. This is necessary to manage them if/when you need to revise them because the client is changing their approved translations.

    - Beware of short TUs. They tend to be ambiguous and the minimum length of a lockable TU depends on the target language.

    I would suggest a variation to your idea: "Lock TUs in the Project TM" - that way you can start over when the "old" TUs eventually may need to be changed.

    Alternatively, you can create a separate TM containing ONLY those permanent TUs that you want to keep. Then pre-translate your project with this TM first and have the process lock all 100% matches. We have been using this process and it works quite well for us.