Hi Martin,
Do language pairs and direction of the project and TMs match? You can revert to the update 14 and then again to update 15 to compare. You can submit a ticket, create a .ctp package of this project via Project > Export > To package... and attach it to the ticket. I will examine it.
Igor
m.brueggemeier
Hi, everyone!
I'm having a big problem. Today, when I started CT and loaded the project that I created yesterday, I noticed that CT no longer automatically searches the TMs and glossaries attached to the project, except for the ProjectTM (the project glossary isn't searched automatically either).
I have not changed any setting that prevents an automatic look-op (at least not intentionally). The "Automatic memory matching" option in the preferences is ticked, and the workflow integration of the TMs is set to "Automatic", not "Manual". Is there any setting that disables all searching in TMs/glossaries (except the ProjectTM) that I might have overlooked?
None of the TM's/glossaries I'm using is particularly large (the ProjectTM and the two read-only TMs are less than 1.5 MB in size altogether), so it can't be a memory problem.
I'm using the build of Update 15 that was uploaded yesterday, and the project was created with the first build of Update 15 (of three days ago). As the problem has never occurred before, I'm wondering if it's related to that update. Could reverting to Update 14 help? I tried with my previous CT project, which was created with Update 14, and CT searches the TMs and glossaries of that project as it should. (BTW, that project is much more memory-consuming than the current one.)
TIA for your advice!
Martin