Save as target file from a translated PPT in Studio 2021.
Can anyone help as I get an error message that shows blocking of the targeted ppt file?
Message received when opening PPT: PowerPoint found a problem with content in zzzz-file.pptx PowerPoint can attempt to repair the presentation. - Repair - Only few of 139 slides show up as translated. The rest greys out without any info.
Does this look familiar to anyone and is there a solution?
Many thanks
L Slowack
I had a similar issue recently and posted a question in the Beta forum. I got two good hints from Daniel Brockmann and from
As I'm, not sure if you follow the posts there, I'll just copy and paste them here.
First the suggestion from Daniel:
Hi Simon Bratina - what I do in this case is to take the original file and roundtrip it without doing any translation - open the source file, copy all source to target, save the target file, open it in PowerPoint. This then tells me if it's sth in the file type itself, or sth the translator might have introduced in the tagging. We can then take things from there I would say.
And here is Walters's suggestion that helped me with pinpointing the problematic segments:
Hi Simon
We have come across this problem a few times already and have not always been able to pinpoint what was the cause. In quite a few cases however, it was due to merging of segments across paragraph boundaries.
When we face this problem, we usually do a full roundtrip by taking the original source file (after checking as suggested by Daniel or using pseudo-translate if the source file can be previewed), then translating it again using a temporary TM created by importing the already existing SDLXLIFF. We don't use the pretranslate batch task, but use 'Translate to fuzzy' in order to spot the places in the document where a segment split or merge has taken place. After every segment merge or split, we check if the file can be previewed. If it can, we save the SDLXLIFF and go on translating to fuzzy. If the file cannot be previewed, we have identified the culprit.
After having translated the entire document this way, we can then generate a working target document. This procedure may sound laborious, but it has always helped us to work around the problem.
Hope the above will help you.
Hi Laurent Slowack and Simon Bratina
The good news is that this problem seems to have been resolved in Studio 2022.
See this post: (+) Praise where praise is due - 2. Trados Studio - Trados Studio - RWS Community
Translate
