Why does Studio 2017 not update saved segments properly?

When I save a segment to the TM and then perform changes on the segment and save it again, the changes will not be updated properly, and the match I will get does not reflect the changed segment but the initial status of the segment when saved first.

This is also true for MultiTerm entries. They just do not update. Even though I delete entries, they will still appear as if nothing ever happened.

Also, Studio 2017 SR1 really crashes significantly often as opposed to earlier releases.

I observed another strange behaviour: auto-propagated segments do not appear in the TM when you set the cursor into this segment in the editor, i.e. they are not recognized as matches.

Would be interesting to know if anyone has made similar experiences.

Parents Reply
  • Hi Marlen,

    Sorry to hear about your frustration. I just wanted to say that this does sound like a LookAhead situation, but since you've already disabled LookAhead, it's a real puzzle. One other thing that caught my eye in your description is the translation results appearing after you've entered a new translation. This points to the TM lookup operation possibly taking too long (longer than it takes you to enter the translation again), and so there must be some factor causing this to happen, which is why Paul and Ali are asking about antiviruses and firewalls. My suggestion would be to disable your plug-ins and then enable them one by one in order to investigate if one of them is causing the issue (of course, testing your environment before re-enabling each plug-in).

    I know it's easy to suspect that something is wrong with Studio when we see effects like this, but this not being a generalized issue for other users means that there must be something in your particular environment leading to this, and so the best course of action is to have SDL Support help if none of the suggestions here are working.

    Best of luck!
Children
No Data