Translate
Version Information
===================
Passolo Translator Edition 2015
Version 15.1.453.0
SDL MultiTerm 2015 SR2
Version 12.2.1629.0
Windows 7 Service Pack 1
Usage Scenario
==============
I am translating a *.tbulic15 file from a large company.
The company provides a Translation Memory and a Term Base via server connections.
All is setup and working for a long time now.
Description of problem
======================
CASE A) Moving without editing works fine
When I move from one editable string to another, without editing anything, the move takes less than 0,5 sec. After the time, I can start editing the new string, while at the same time hits from the different resources (index, TM and TB) appear one after another in the "Term Recognition" and "Translation" panes. After a few seconds, sometimes more than 10 seconds, depending on the number of hits, all hits are loaded, and I can use them as needed. At this point in time I am often already finished with typing the translation.
CASE B) Moving after editing creates delay
When I move from one editable string to another, after I have changed something in the first string (like added or deleted just one character), it takes 13 seconds or more, before I can start editing the new string. During the 13 seconds or more, I sometimes can see the hour glass (actually the hour circle, as I use Windows 7). Then, after the hour glass has disappeared, and editing is released, hits from the different resources start pouring in. For a project which usually requires 10 hours working time, this effect creates at least 6 extra hours, which I simply spend waiting (based on the assumption that I touch every string three times on average). But the single delays are still too short to have a coffee in the meantime ...
The only way I found to remove the delay in CASE B, is unloading the SDL MultiTerm Add-in. This is obvious not a workable option. At the moment I have no access to the client, so I cannot ask for a local version of the term base. And it is likely it would be refused anyway due to the policies of the organisation.
The delay has appeared with some minor or major passolo update (I believe with the update to Passolo 2015), but with the last minor update it has worsened to an extend that is no longer tolerable.
