• Replies 5 replies
  • Subscribers 434 subscribers
  • Views 2203 views
  • Users 0 members are here
Options
Related

Will we ever get two-directional TMs with Trados?

Pavel Tsvetkov

All other major CAT tools reuse the same TM for both directions, while Trados remains unable to attain this simple feature. Nothing in the press release about v2019 makes me believe that things are going to change any time soon. Or maybe an insider can prove me wrong?
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion

  • I use my EN-ES TMs for ES-EN with AnyTM, did you have in mind something different?
  • Studio doesn't use bi-directional TMs because of the way it supports context. However, you do have AnyTM which allows you to add your TM to your Project Template once and then use it in both directions thereafter. Why is this feature so important for you?

    Paul Filkin | RWS Group

    ________________________
    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

  • in reply to Paul
    Hi Paul,

    1. With Trados TMs being as big as they are (and doubling in size after "upgrading" them) why would I want two unidirectional TMs instead of one?
    2. And I have to now use both of these unidirectional TMs for, say, every Technical project for every new client to make sure they are both updated equally? Is that practical or even possible?
    3. This does not strike me as the optimal solution to the problem and for one reason or another, both Déjà vu X3 and MemoQ have solved the riddle long ago. Both use smaller TMs and they are bidirectional.
    4. Incidentally, Déjà vu X3 also reuses better recently translated segments from the current project. Actually, Trados is not able to do that at all, as AutoSuggest Creator is a static, not dynamic feature, and it has a minimum size requirement.

    Best regards,
    Pavel
  • in reply to Pavel Tsvetkov

    Hi  

    Unknown said:
    both Déjà vu X3 and MemoQ have solved the riddle long ago. Both use smaller TMs and they are bidirectional.

    This is a silly argument.  Comparing the way the tools work like this makes no sense unless you compare all the features together.  They are different and just because you don't use all the features of a Studio TM doesn't mean it should be changed.  Don't get me wrong... I'd like to see a unidirectional TM and small sizes too... but you are over simplifying the task.

    Unknown said:
    Incidentally, Déjà vu X3 also reuses better recently translated segments from the current project. Actually, Trados is not able to do that at all, as AutoSuggest Creator is a static, not dynamic feature, and it has a minimum size requirement.

    Huh?  Why are you talking about AutoSuggest Creator when you have UpLift that does a very good job of leveraging subsegment content in real time.  You seem to be complaining about the upgrading size and then not taking advantage of any of the benefits.

    Paul Filkin | RWS Group

    ________________________
    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

  • With its 7 suggestion engines, plus orange wrench marker, plus orange F marker, plus green-barrel-riding-a-grey-bike marker, plus double rectangular marker....... I have to confess that Studio is second to none of its market neighbors in terms of suggestions. One of them (autotext) even does not require any source to parse with.

    Only one thing to regret is that AnyTM functionality does not seem to work with GS TMs. I can add a file-based TM in a GS project and it works well, but adding a server-based TM to the same GS project does not F3-find what it F3-finds with the file-based TM.