• State Suggested Answer
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 434 subscribers
  • Views 2314 views
  • Users 0 members are here
Options
Related

Studio 2017 and term recognition

Enrico Cau

Long story made short.

 

Term recognition doesn't work properly in Studio 2017. Terms appear in the proper window but they are not suggested in the editor (they don't show as quick insertable terms). I have tried everything. Rebuild the MT database, tuning options, deleting and reinserting terms that can't be recognized and so for and nothing works. Paradoxically, the first iteration of Studio 2017 had everything working fine, so fine that i rarely needed to type translations while now i see the term and i need to insert it manually because it doesn't show up in the drop down menu while typing. This is now happening for hundreds of terms in a termbase of about 3000 terms and it's taking a toll on deadlines. I didn't expect this. It's happening not just in one case but also with different projects.

 

Any solution for this?

 

Thanks

 

Enrico
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
  • 0
    Hi ,

    If you see the terms are recognised then the autosuggest is controlled through the settings in File -> Options -> AutoSuggest. Make sure that "Termbases" is activated and that you have checked "Enable AutoSuggest".

    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

  • 0 in reply to Paul
    Hi Paul,

    And thanks for the kind reply. Termbase is 3000 words big at the moment. Studio has a variety of issues in this case, the above being just one. Before i proceed please note i have rebuilt the TB, reorganized, created a new template for the project, set all options as per your suggestions (and tried different variations on both main File/Options and Project/Options menus). The issues are as follows:
    - Sometimes i get a "can't add term to termbase" message. This requires closing and reopening the whole Studio session.
    - Sometimes the term appears clearly present in termbase (red line over it in the source section of editor window) but it won't show in the term recognition window. However, if you try to re-add it, you will get a message asking you if you want to MERGE the term because it is already existing (but it is not suggested)
    - The problem i mentioned in my first case. The term is there, visible in the upper right window of term recognition but Studio won't suggest it.
    - The issue reflects in the QA check, where non-existent terms are "suggested" as missing with the QA asking me to amend a term that is not present in the segment. I am not sure whether these are related but the whole thing looks really odd.

    Example
    English: The machine ABCDX can be switched on by pushing button A, on the right side of the main panel
    Italian: La macchina ABCDX può essere azionata premendo il pulsante A, posto sul lato destro del pannello principale.

    Term Recognition shows: Macchina ABCDX (previously added by me)

    I start typing Macch...and nothing shows....then i have to type it entirely manually.

    At QA: The correct term for "Arbritrary TB term here" is missing.

    This does not happen with just one TB but with a number of them, all of them pretty big and often with similar terms. I am not sure this is about settings anymore. Also, i am not sure what's going on but i had many more segments, fuzzies etc leveraged with the first iteration of Studio 2017. It was doing really well. I don't know when and why things went south but it's not working as expected.

    Thanks

    Enrico
  • 0 in reply to Enrico Cau
    Dear Enrico,

    I do not know whether you have meanwhile resolved this issue, but I experienced the same and now term recognition is working: terms are recognised, and if I type the first letter, the term is suggested. This is what I did:

    I created a new, empty termbase in MultiTerm 2017. Then I opened my existing termbase (which I created and used in Studio 2015) and exported it to XML. Subsequently I imported that XML into my new, empty MultiTerm 2017 termbase, after which it contained all the same terms as the 2015 termbase. When I now use the 2017 termbase in Trados Studio 2017, term recognition works. I hope this is helpful to you.

    Best regards,

    Marcel Steur