unknown error when reading plug-in filter definition file

Question

Trying to export a .ppt file. Can't either "Export for external review" or "Export files". I don't see any answers for a couple of similar questions. 
 It was originally missing the dependency file, but I seem to have found a workaround for that.

Donal Lyons · Accepted Answer

Hi Paul, 
 
Sorry, I had a looming deadline. 
 
1) I had already tried to add Trados to the Norton exceptions but Adrian pointed me at a different folder and, once that was done, the filter issues stopped happening. I really think you need to formally issue users with a list of products that cause this issue - it has, after all, been going on for years and is well-known. It seems odd to me that your software people haven't been able to resolve it; it's not as though this happens with any other of the many software products I use. 
 
2) I'm still not 100% sure why some segments were appearing as untranslated. I was following the procedure I've used many times in the past of confirming segments as translated, of periodically updating Main and Project TMs, and of saving. That has always allowed me in the past to clear all target segments and then pull them back automatically from the TMs as translated segments. Not having them gave me three extra rounds of proofreading amounting to a full days work. 
 
3) This time my procedure was giving me 99% matches and I'm not clear why - the TMs should have had 100% matches for the segments I'd saved. That wasn't a problem as such, the 99% matches were fine to work with, but I don't understand why they wouldn't be 100%. 
 
4) It's odd that the registry had no keys for Trados - I did a perfectly standard install when I upgraded to 2014. But again, that doesn't seem to have been part of the problem. 
 
Regards, 
 
Donal.

Paul · Answer

Hi Donal, 
 
You haven't told us what version of Studio you are using; this is always useful. Presumably this is also a source PPT and nothing else, so not a TTX based on a PPT? 
 
Thanks 
 
Paul

Paul · Answer

Hello Donal, 
 I have sent you the translated PPT and my version of the SDLXLIFF. I was able to reproduce the problem with your SDLXLIFF so I think something has happened specific to your environment that caused this problem... not sure what exactly, but these things can happen as a result of aggressive software such as some Anti-virus applications, clean up tools, defraggers etc. Studio writes to temporary files while you work on them and if anything happens to these files you can have problems. So I don't have a good answer to why this happened, only guesses. 
 Here's how I resolved it though after we proved the PPT itself should roundtrip ok. 
 
 I opened the PPT using the single document approach and created a new single file project 
 I created a new Translation Memory 
 I imported your translated SDLXLIFF into my new Translation Memory 
 I pretranslated the file (I checked include draft and reduced the match value to 90% just as a catch all for small differences between your setup and mine) 
 I saved the target 
 
 This worked and I sent you my SDLXLIFF and the translated PPT. You won't need to take the same approach as I did because you should already have a Translation Memory. But that process is a good one if you have this kind of problem in the future... hopefully not too often! 
 Regards 
 Paul

Paul · Answer

Hi Donal, 
 
There is clearly something wrong with your environment. I have not had any of these problems, even if I use the now no longer supported Studio 2011 which you are still using. TMs do not just lose edits if you have saved them as you work. 
 
Can you try Studio 2015 in this environment and if the problem still continues with this version we can arrange for a support engineer to take a look at what might be causing the problem. I can't do that if you're using Studio 2011. I can put a trial license into your account so you can try it for a little while first? 
 
Regards 
 
Paul

Paul · Answer

Sorry Donal... getting users mixed up. You're on Studio 2014. Let me arrange for someone to have a look at your environment and see if we can figure out what is causing your problems?

Paul · Answer

Hi Donal, 
 
We didn't hear back from you and I'd like to close this off. I believe one of our support engineers, Adrian, sorted this out with two things: 
 
1. Explanation of why you were getting target docs with source still in there, and 
2. He added Studio to your AntiVirus exception list 
 
I hope this completely resolved your issues? 
 
Regards 
 
Paul

Trados Studio > 1. Trados Studio

unknown error when reading plug-in filter definition file