Cyril A. 

Have you tried providing these target files to your client, or did you create the original powerpoint and then translate it?  Sometimes this is a result of different versions of Office and you might see a problem that your customer does not.

Hi Paul 
Same problem here.
We work with and all employees use the same Office version as it is deployed by our IT department.

When this problem occurs, we perform a TM export filtering the TUs according to the project number and create a local project specific TM. Then, we prepare a new project with the affected file(s) and pre-translate them using only the new project TM. Afterwards, we finalize this new project, delete the sdlxliff and the target file in the original project's target folder and replace them with the ones created in the local project.

It's a smooth but time-consuming workaround. If there was any other way to handle this issue, I would highly appreciate your advice.

Thank you

Seraina

Hi Paul 
Same problem here.
We work with and all employees use the same Office version as it is deployed by our IT department.

When this problem occurs, we perform a TM export filtering the TUs according to the project number and create a local project specific TM. Then, we prepare a new project with the affected file(s) and pre-translate them using only the new project TM. Afterwards, we finalize this new project, delete the sdlxliff and the target file in the original project's target folder and replace them with the ones created in the local project.

It's a smooth but time-consuming workaround. If there was any other way to handle this issue, I would highly appreciate your advice.

Thank you

Seraina

Apologies, forgot to insert the Trados Studio version we work with: Trados Studio 2022 SR2 - 17.2.9.18688

Seraina Hartmann 

I'm not aware of another way.  I'm not even sure what causes this in the first place!

Hello Seraina Hartmann ,

With the risk of looking as dumb as our Community AI: why don't you update your Studio 2022 to 17.2.12? You never know!