Hello,

It seems that you're experiencing an issue with your translation memory not automatically populating the segments in your local document. To resolve this issue, please follow these steps:

Step 1: Ensure that the correct translation memory is connected to your project. Go to the "Project Settings" and check the "Language Pairs" tab to confirm that the appropriate translation memory is selected.

Step 2: If the correct translation memory is connected, try updating the translation memory from the cloud. Go to the "Translation Memories" view, right-click on the translation memory, and select "Update from Cloud."

Step 3: Once the translation memory is updated, open your document in the Editor view and go to the "Review" tab. Click on "Pre-translate" to populate the segments with matches from the translation memory.

Step 4: If the issue persists, consider creating a new project with the same settings and import the document again. Make sure to connect the updated translation memory to the new project.

By following these steps, you should be able to retrieve the translations from your translation memory and apply them to your local document. If you still encounter issues, you may want to consider working exclusively in Trados Live / Language Cloud until the problem is resolved.

Best regards,

As it seems the memory loaded is indeed not the correct one. The problem is that now I cannot find the Translation engine that had the memories I worked on until now. It does not show on the language pairs menu. The file I translate is local and not on cloud and the languages on the engine I used and cannot find were from language A->B. The file is from languge B->A. Could this be the issue?

Hi Marijana Milunovic 

Yes Translation Memories are direction specific so it could be the direction is causing you this concern

Lyds

The Translation Engine I had previously used has TMs with both directions between the languages (source and target) but It does not appear as I tried to add them to the project I worked on. I had never had trouble with projects being cloud based but this project was local. Is it possible that my Translational Engines can only be used in cloud based projects?

Futhermore, I had another disopointing experience. The funcitionig of Trados got even worse. I translated a document in excel form using Trados and than I extracted the file in the same format upon completion. The problem is that the file extracted was apparently an earlier version I had worked on and had plenty of mistakes I had later corrected. This was a very frustrating situation since it costed me time, money, and client. I have checked the file before I extracted it from the desktop version of the software. Is it possible for this mistake to have occurred from a conflict between the cloud version and local based file? It was a really serious problem.

Futhermore, I had another disopointing experience. The funcitionig of Trados got even worse. I translated a document in excel form using Trados and than I extracted the file in the same format upon completion. The problem is that the file extracted was apparently an earlier version I had worked on and had plenty of mistakes I had later corrected. This was a very frustrating situation since it costed me time, money, and client. I have checked the file before I extracted it from the desktop version of the software. Is it possible for this mistake to have occurred from a conflict between the cloud version and local based file? It was a really serious problem.

Marijana Milunovic 

It sounds more like a problem resulting from you using OneDrive perhaps?  OneDrive is notorious from causing synching issue problems if yo save your projects on a drive linked to the OneDrive backup.

If you really think the problem could be related to you using Cloud then why don't you generate the target from the cloud and see if that fixes it.  At least using Trados Cloud solutions won't suffer from OneDrive problems.