This message is mostly caused by the following problems in the source document:
Comments in Word documents, especially by multiple authors.
Delete all comments from the source document and put them back in again after translation.
Footnotes in Word documents that do not comply with the rules for footnotes, such as those containing automatic lists or paragraph marks.
Remove the offending footnotes from the source document and insert correct ones.
Once you have corrected the source document, you need to set up your Trados project again. Apply the translation memory that has already been filled.
The "tab-delimited text file" format was probably selected instead of "plain text" when it was saved.
This error message can be caused by a number of things. Try the following series of solutions:
SDL Trados Studio should run now, but all the projects will have been removed from the project list.
If you have to set up your project again or if, for whatever reason, the target segments have to be filled in from the translation memory again, SDL Trados Studio has a function called "Confirm and Translate until Next Fuzzy Match" (riboon "Home" tab > "Segment Actions" group > dropdown menu under the "Confirm" button).
This function looks for matches in the translation memory. If a 100% match is found, then it will be inserted into the target segment, the segment will be confirmed, and the next segment will be opened. If no 100% match is found in the translation memory, then the cursor will stop.
Unfortunately, the function does not always work smoothly. There are two options to get around this:
Option 1
From now on, all applied 100% matches and context matches will automatically be applied and confirmed.
If a lower Quality match is inserted, you will have to confirm it manually before moving on.
NB.
After finalizing the Project, remember to go back to the "Options" dialogue and deactivate the "Confirm segment after applying an exact match" option again.
Option 2
The document will be opened in the Editor with the pre-translated segments.
No suggestions are displayed in the Term Recognition window, despite MultiTerm databases being correctly configured.
Term recognition should now work.
Sometimes, Term Recognition fails to find terms which are actually in the MultiTerm database. This can be because the search depth value is too low.
If you want to set a higher value for Search depth by default, use the setting under File > Options.
Although the Translation Memory is correctly configured, only a blank space is displayed in the Translation Results window, without labels.
If you want to set a higher value for Search depth by default, use the setting under File > Options.
Sometimes Word cannot open the target text of a translation, giving the following error message:
The file xxx.docx cannot be opened because there are problems with the contents.
If you click on the Details button in the message window, an error description similar to this will appear:
The name in the end tag of the element must match the element type in the start tag.
Location: Part: \word\document.xml, Line: 2, Column: 2260
According to SDL, the new file filter for Office 2016 formats is very sensitive to repeated overwriting of target texts. This is not a bug in the program, but does give an insight into the future. The intention is that, in a future Studio version, it will be impossible to overwrite an existing Microsoft Word document using the Save Target As function.
To get around this problem, you can try the following workarounds:
Workaround 1
Delete the existing saved target text before saving a new version.
Workaround 2
Give your target text a new version number each time you save it.
Workaround 3
Assign another file filter to the project:
The workarounds work the same way for PowerPoint presentations.