This article is written to help with troubleshooting issues with target generation.

There are three main target generation issues that can happen:

  1. Target does not generate at all.
  2. Target is generated but there is an error or warning when you try to open it.
  3. Target is generated but some text is missing or has wrong formatting.

If your target is not being generated at all, you should first check if XTM is able to give you the reason why.

To do this navigate to Project Editor -> Files -> Target language that has the issue and click on the red exclamation mark icon:

You will be shown a message with an error log. Very often this message can inform you what exactly is wrong with your file, like on an example below:

If the message did not point you to what's wrong with the file you can now create a simple test project.
You need to create a project that is exactly the same as your original one (same customer, language combinations, etc.) and try to generate the target file in there. If the target file still has the same issue you should also check for inline issues and try again.

Checking for inline issues

Inline tags can contain text formatting and file structure information, as well as custom variables. While they generally can be moved to fit the translation, it is also possible to misplace them.

Misplacing inline tags can cause the target file generation to fail, but it can also cause the generated target to have wrong formatting, some parts missing, or to not open at all and show an error.

To search for misplaced inline tags do the following:

  1. Go into the project's General info page
  2. Find the QA profile and click the pencil icon to edit it:

  3. Uncheck all checkboxes except for the one in Other section called Order of inlines is changed or content is missing between inlines in target segment:

    This change will only affect this specific project. Save the general info page.

  4. Open the problematic file in Workbench and run the QA for the document to show only segments with warnings:

    Mark to check ICE and 100% matches as well:

  5. Once it's done please review the segments to find any inline tags that have their order changed incorrectly.
    The most common issues with inline tags are:
    • nested hyperlinks and similar
      A hyperlink cannot be nested as it cannot direct to two places at once. This always causes issues in the target file or in target generation.
    • text outside of its proper structural bounds
      In many files text can only appear inside specific elements (like <t> text formatting inline tags in xlsx files) and cannot in other (like in <menucascade> in some type of XML files). If the text is put there it will either not be displayed in the file (with a warning that something went wrong and your editor will want to recover as much as it can) or the file won't open at all and will give an error.
    • text moved to different structural bounds
      In files like docx, it is possible to use a style that hides the text and by default, this text is not extracted for translation. The inline tags containing the information about this text style can sometimes be moved in a way where they hide the translated text as well.

  6. If the file was generated correctly after fixing inline tag placement then it might be good to revert QA check to the previous unmodified one. To do this go to the project's General info page, find QA Profile, and choose your usual one from the dropdown list:

  7. When you reviewed segments and fixed potential issues, but the target still is wrong or is not being generated it's time to open a ticket to our support.

    When creating a ticket for our support please include the following information:
    - the URL you are using to log into XTM
    - company name you are using to log into XTM
    - project name or id
    - affected file name
    - affected target language