• State Suggested Answer
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 432 subscribers
  • Views 1311 views
  • Users 0 members are here
Options
Related

Fields in TB recognition not showing until TB is removed and re-added

Leonardo Pardo

Hi,

Since some time ago, every time I switch projects, term recognition does not display the entries Fields. When I check the "Field Selection" window, I surprisingly find the name of the TB from the last project I worked on at the top of the tree instead of the name of the TB for the project I am currently working on. The only solution I found is to remove the TB in Project Termbase Settings, close Trados, re-open Trados and then add it again. Only then the TB name and the fields display correctly.


Why is this happening? Is there a less convoluted solution?

 

Thanks for your help.
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0
    Hi ,

    Is this related to you creating new Projects with an out of date project template coming from your File -> Options? The Project Settings are specific to each Project and don't transfer from one project to another.

    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
    @ Paul. Leonardo is a member of our team at Precision Translators in Colombia. He is a translator, so he is not creating projects. His workflow is received automated email from GroupShare. Open server project. Checkout appropriate file, and get to work.

    What he is saying is that the TM Field settings configured through the Hitlist Settings Window, and which are specific to the users workstation, are not being preserved from one project to the next as they should be.

    Example, he has his install of Studio configured so that it should show the Definition field for the Source and Target term when there is a Term hit displayed in the Term Recognition Window. That is working fine in the current project, but in the next one he has to reconfigure as described above.

    This has not been a problem in the past, and he has been doing it since 2011. Our feeling is that it is an issue new to 2017.

    Thanks, Andrew
Reply
  • 0 in reply to Paul
    @ Paul. Leonardo is a member of our team at Precision Translators in Colombia. He is a translator, so he is not creating projects. His workflow is received automated email from GroupShare. Open server project. Checkout appropriate file, and get to work.

    What he is saying is that the TM Field settings configured through the Hitlist Settings Window, and which are specific to the users workstation, are not being preserved from one project to the next as they should be.

    Example, he has his install of Studio configured so that it should show the Definition field for the Source and Target term when there is a Term hit displayed in the Term Recognition Window. That is working fine in the current project, but in the next one he has to reconfigure as described above.

    This has not been a problem in the past, and he has been doing it since 2011. Our feeling is that it is an issue new to 2017.

    Thanks, Andrew
Children