Hello Suzanne,

I understand that you're having trouble with a PowerPoint file in Trados Studio. This issue has been resolved in the latest version of Trados Studio, so updating your software could be the easiest solution. However, if you prefer to keep your current version, you can follow these steps:

Step 1: Recreate the project using the previous Microsoft Power Point 2007-2013 (Power Point 2007 v.2.0.0.0) filter.

Step 2: Open Trados Studio and navigate to File > Options > File Types.

Step 3: On the right-hand side list, disable the Microsoft Power Point 2007-2016 filter and ensure the Microsoft Power Point 2007-2013 filter is enabled.

Step 4: Confirm this setting by clicking on the OK button.

Step 5: Import your PPTX source file again for translation by either selecting 'Create new project' or 'Translate as single document'.

Step 6: If you have a translation memory that was used for the previous translation and you have updated it with the new segments, use it for this one as well.

Step 7: To import your previously translated segments into this new one, you can either use the Pre-translate or Perfect Match batch task or both.

Step 8: Save a new target file (Save Target As / Shift+F12) and open it.

Please note that the segmentation in the new bilingual (.sdlxliff) file may be slightly different compared to the previous one due to the different file type used. Applying the Pre-translate or Perfect Match might not result in the same percentage of translated and confirmed segments as in the original bilingual file.

I hope this helps! If you have any other questions, feel free to ask.

Best regards,

RWS Community AI

Dear AI, please read your knowledge base:

What are you talking about?

Also, read this thread and try again...
community.rws.com/.../powerpoint-files

Stepan Konev 

Stepan Konev said:

Dear AI, please read your knowledge base:

You do know he's not a real person ;-)

Stepan Konev said:

What are you talking about?

He/it did say:

RWS Community AI said:

This issue has been resolved in the latest version of Trados Studio,

Seems that could be correct.  It then attempted to offer a solution if the user didn't want to upgrade.

You said:

Stepan Konev said:

This was caused by a defect which affects the latest Microsoft PowerPoint 2007-2016 (PresentationML v. 1) filter in SDL Trados Studio 2017 and also 2019 early versions. and it has been fixed in the latest version of Studio 2019 SR2 CU8 / Studio 2021 / Studio 2022

Whilst it didn't use this specific example it did go a bit further and tried to help.  How effective that help was remains to be seen, especially as we don't know what version the user has.  But doesn't look like a terrible response to me.

Paul said:

You do know he's not a real person ;-)

Definitely I do. But it mimics a real person.
One good thing here is that my reply has drawn attention of a real expert. Probably you can help. It is about Trados 2022.

Stepan Konev 

Stepan Konev said:

Probably you can help. It is about Trados 2022.

Is it also the exact same issue raised here?  If it is, can you share the PowerPoint?  You can email it to me if needed - pfilkin at sdl dotcom

Paul said:

can you share the PowerPoint?  You can email it to me if needed - pfilkin at sdl dotcom

suzanne deveson  

Hi Paul,

Thanks for responding. Stepans link to the earlier post actually helped me solve the issue. I created a new project with the source file (translating a single file), using the TM I used for the other project, I pre-translated the file and then saved the target. No idea why that worked, but it did. The AI response was a bit confusing, as I use Studio 2022 and Microsoft 365, so the information about the earlier version of Studio and PowerPoint was not helpful.

Hi Paul,

Thanks for responding. Stepans link to the earlier post actually helped me solve the issue. I created a new project with the source file (translating a single file), using the TM I used for the other project, I pre-translated the file and then saved the target. No idea why that worked, but it did. The AI response was a bit confusing, as I use Studio 2022 and Microsoft 365, so the information about the earlier version of Studio and PowerPoint was not helpful.