Sorry, was sitting with Osama of the WB and posted from his laptop.

We encounter this with our large TMs so a good solution would indeed be great.

Osama

Sameh Elsharkawy Osama Abdel-Hameed

Osama Abdel-Hameed said:

I have had this discussion with Paul a while ago and I believe this really deserves a second look, and if not, then having a solution to research TMs in a faster way outside the editor is indeed very much required

We actually spent quite some time with a developer looking at how we could integrate DT Search into this workflow.  But the APIs are not capable enough in DT Search to support this.  I think the solution is probably to look at creating a new TM Provider based on a technology that can support larger TMs with ease.  This is something we did start to look at earlier this year with the AppStore development team, but we have been distracted with other priorities.  We will come back to this because handling large TMs in Studio with the current technology isn't really workable.  I upgraded a TM with three and a half million TUs last week and this does work.  But I now have a TM that is 24 GB in size and frankly unworkable as a sensible and performant TM... as you have pointed out.

We do hope for a solution to this indeed Paul. Osama and I use text to speech technology when reviewing documents (the final check before packaging any translation to our clients) and we do need to consult the TM from time to time for a term or more context, etc, so this would indeed be a big boost. Thanks for all your efforts.

Sameh