You are currently working on UAT 

Studio 2019 TM strange (faulty) behavior

Hi

It seems that Studio 2019 in not doing a proper job of updating main translation memories and in populating the translation file through pre-translation and thereafter. My current example is this:

I received a PDF file for translation (not scanned, but "open"), I converted it to plain text and opened a project for it. Subsequently, the client sent me a word file of the same PDF file with minor conversion variations from my file. I started a second project with the client (second) file, worked on it for a while, but then decided to go back to my original conversion project. I updated the main translation memories in the second project, and pre-translated the first project again. To may astonishment, not all segments were transferred to the first file, even if they were identical. Moreover, certain identical segments were not even subsequently identified as a partial match. Identical segments between the two files seem to have simply vanished and not recorded in the TM.

This behavior was identified previously about two years ago, but also since.

Can this be explained / repaired? this is very bad for translation productivity to say the least.

Best

Shmuel

Parents Reply
  • I wonder what you are trying to find in that text that is not Studio's fault. Failure to detect a corrupted feature of a document that prevents Studio from processing it properly (saving it to the TM), as well as failure to record and save a segment in a project to the TM for any other reason, both require notification to the user. I did not receive any notice of any problem of any kind. One way or the other Studio should have done something that it did not do, either save the information properly and than retrieve it properly, or provide appropriate notices of failure to do so.

    Regardless, I will prepare a small word file for you tomorrow and send it here so that you can check what you need.

Children
No Data