Under Community Review

Fix the issue with duplicate TU creation in AnyTM

As stated in the title, I'd like to have AnyTM behave just like a regular TM, without duplicates being created when a TU is edited during translation.

Nora Díaz

  • Hi Wojciech,

    I don't actually use it that much for the reverse language pair, although I have used it occasionally, especially for a client who translates materials in both directions and it's just convenient to have everything in the same TM. My main use of AnyTM is for language variants. I have a master TM that is set up for ES-MX and I often need to add it to projects that are set up for ES-LA and ES-US, for example. So as you have mentioned, the benefit is that I don't have to keep track of separate master TMs, but the downside is the issue with fragment matching and duplicate TUs.

  • Hi Nora. Since you know your way around Studio, I have a question. Is there any real benefit in using AnyTM as a reverse TM?

    I mean, from what I can see, it's better to have two big mama TMs and consistently update them with data from project TMs, than create AnyTM, which BTW is incompatible with Fragment Matching.

    So, what's the benefit apart from the fact that the whole process is a bit faster?