• State Verified Answer
  • Replies 3 replies
  • Subscribers 432 subscribers
  • Views 2019 views
  • Users 0 members are here
Options
Related

SDL Studio 2017 and MultiTerm pane in Editor view

Claudio Nasso

Good morning,

granted that my first SDL CAT I bought in 2005 was SDLX, I’d like to recall a SDLX feature that I have found quite useful at that time.

If I remember well, and if I am not in error, SDLX had a feature/command to automatically insert MultiTerm/Termbase concordances in all target segments (no matter if they were already translated or not yet translated). I have not found this feature in the subsequent 2007/2009/2011/2014/2015/2017 SDL Studio editions.

There is a chance that I have “dreamt” it and that my brain is trying to recall something that, in fact, is just “imaginary”.

Could any “old user” of SDL products confirm the real existence of this feature and, if I am right, could any SDL programmer/guru tell me if is there any chance to rise again from ashes this function?

At present (Studio 2017), apart the activation of “Termbases” in the “AutoSuggest providers” section of the “Options > AutoSuggest” window, the only available alternative to insert a MultiTerm concordance is to individually select the translated term present in the Termbase pane, right click on it and select the command “Insert term translation” (and there is not any available shortcut).

Thank you for your comments/thoughts.

Claudio
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

    Hi  

    I guess  or  could confirm the behaviour in SDLX (or maybe any SDL translator!)... I don't know SDLX well enough.  I can tell you there was a feature like this in the old Trados:

    Studio doesn't have this feature, but you could use the Terminjector to achieve this.  The drawback of course is that this would not use your actual termbase and you'd have to create a separate rules file for it as well as use this TM provider for your work... at least for the pretranslation.

    I think the reason it never made the Studio product, if I recall the discussions correctly from years ago was that there was some doubt over its usefulness given ambiguities over things like which term to choose when you have synonyms or homonyms for example.  So it was removed and I think including this post I can only ever recall this question being asked three times!

    I think it is something that could be done using the API but would probably have to set down some rules such as first come first served for the synonym/homonym problem... or perhaps make it an interactive process and stop and ask when an ambiguity is found.  Might be interesting for a developer with the time to do it.  We would not do this with the community developer team unless there was thought to be good value in it and then we'd have to fit it into our priority list which is already quite long.

    Why don't you submit this as an idea and then we can find out how many people would be interested in such a feature?

    Regards

    Paul

    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

Reply
  • 0

    Hi  

    I guess  or  could confirm the behaviour in SDLX (or maybe any SDL translator!)... I don't know SDLX well enough.  I can tell you there was a feature like this in the old Trados:

    Studio doesn't have this feature, but you could use the Terminjector to achieve this.  The drawback of course is that this would not use your actual termbase and you'd have to create a separate rules file for it as well as use this TM provider for your work... at least for the pretranslation.

    I think the reason it never made the Studio product, if I recall the discussions correctly from years ago was that there was some doubt over its usefulness given ambiguities over things like which term to choose when you have synonyms or homonyms for example.  So it was removed and I think including this post I can only ever recall this question being asked three times!

    I think it is something that could be done using the API but would probably have to set down some rules such as first come first served for the synonym/homonym problem... or perhaps make it an interactive process and stop and ask when an ambiguity is found.  Might be interesting for a developer with the time to do it.  We would not do this with the community developer team unless there was thought to be good value in it and then we'd have to fit it into our priority list which is already quite long.

    Why don't you submit this as an idea and then we can find out how many people would be interested in such a feature?

    Regards

    Paul

    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

Children