I just installed Trados Freelancer 7.1 in my Desktop. My PC runs on Windows XP which has MS Office 2007 in it as well.
This tool(TRADOS) offers more PITFALLS & POTHOLES than anything else. It is hypercomplicated. It looks like it was not designed for translators but for computer scientists or computer buff-related people or something like that. I've followed all the steps to the letter and then when I click on the "Open/Get" button( Trados toolbar with the flagman at the left, I mean) the Workbench displays the same fateful error message : "(33353): END OF PARAGRAPH NOT FOUND."
In trying to correct the problem, I've placed a paragraph mark at the end of the first segment and made changes concerning the font style as well. Nope. Nothing works. The same error keeps displayed at the bottom of the Workbench.
I am about to give up. I enrolled in a Trados webinar that was supposed to start yesterday but the guys either at Trados or Webex( I have no clue about who the hell made the mistake) e-mailed me with the wrong information involving the time(I am living in North Carolina, U.S.A). I did handle the time difference perfectly and was right on time when the event was supposed to start. I missed it.
So, upon reading what you described below, I thought you might have a different approach concerning this matter and would give me some ideas about how to deal with this ERROR.
In advance, thanks a lot for your feedback on this concern.
When I searched the web for advice on how to deal with the ridiculous amount of installation, execution, corruption and incompatibility issues I've been experiencing with the above in various combinations, I had no idea how many people would have had similar and other problems. This should barely qualify at beta software, it's an absolute mess.
On one job alone, I have just had the misfortune to suffer the following problems at the hands of Trados - bearing in mind that the actual work to translate the files in question all had to be worked around these problems.
- When initially trying to run Trados 2007 with Word 2007, I got error 33353, end of paragraph not found for every segment.
- Then with Word 2007 uninstalled and Word 2003 installed, the Trados 2007 then shut down immediately every time I opened it, with a message claiming that an instance of Trados was supposedly already running, but wasn't.
- Incompatibility with files (error message from Trados: "no translatable content in files") means files can't be pretranslated or manually edited and then used to update the TM
- Error 50052 repeatedly, no workaround possible - deleting iix file leads to iix file missing error, TM can't be exported, can't be updated because of first error
- Segments that contain e.g typos aren't updated once corrected manually in files then TM supposedly updated, incorrect segment is still contained in and propagated by TM no matter what I do.The original incorrectly translated segment occurring in file is seemingly skipped or ignored even if segment is corrected directly in TM using concordance function.
I ended up installing, uninstalling and reinstalling various configurations and versions until eventually (literally days later) I managed to get Trados 2007 working with Office 2003. Well, "working" - most of the above issues still occurring periodically.
All this trouble on a single translation job - it has been an utter embarrassment, repeatedly having to explain various and increasingly ridiculous problems to my customer which frankly I wouldn't believe myself at this stage if I wasn't the poor fool having to endure and work around them.
And to add insult to injury, as a freelancer - and one of the first registered users EVER of Trados since its conception, as they once informed me with reverence - I'm not entitled to support unless I buy it, which of course I can't really afford for a single utterly problematic piece of software which they're effectively using me to test, and shouldn't have been released in this condition for free, let alone for purchase.
The SDL (lack of) Knowledge Base doesn't even include any information on solving issues with Trados 2007 yet, presumably because if people knew how full of bugs it was they might think twice about buying it.
More trouble than it's worth in my experience.