Since CU 9 for Trados Studio 2017 (Build 14.1.10009.15268, Released on 21 February 2018) has been installed we have issues regarding text insets in FrameMaker MIF files.

https://gateway.rws.com/csm?id=kb_article_view&sysparm_article=KB0027380

When selecting the "Generate target translations" menu under "Batch Tasks" the error message "Extra 'table' reference tag within the segment ID". Please run the Tag Verification to see detals" is displayed for many files. As a result Trados does not generate the corresponding target MIF files. Unfortunately the message is imcomplete so that you cannot locate the exact position in the files where the issue occurs.

We still can generate target MIF files when the corresponding Trados project has been created before CU 9 has been installed (Batch Tasks "Generate target translations").

When this issue occurs in Trados projects which have been created after CU 9 has been installed we have to ask our freelance translators who still work with Trados Studio 2014 to generate the target files for us. However, not all the files can be generated with Studio 2014. (It does not work for some files). In the case of the files for which it does not work we have to convert the text insets to normal texts and translate the files again.

The description for CU 9 on the Trados page lists a correction regarding text insets: "Text Insets were imported from translation even when the option to import them was disabled. This is now fixed."  We assume that this is the cause for our current issue.

The files which have been created as a Trados project by Studio 2017 but generated as target files by Studio 2014 have some errors, too. These target files contain additional texts (the same texts that can be found in the text insets). However these texts can be edited and they are not translated; they are displayed in German (language of our source files). If the files were correct, they would only contain text insets.

We did not have such issues before CU 9 has been installed. We did not change our files regarding the contents and the procedure (same use of text insets).

We would be glad to provide you with some example files via e-mail. Please contact us via e-mail.
We hope that the issue will be fixed in an upcoming CU.