| Table of Contents |
|---|
...
Issue description & Solution
Target does not generate at all: inline tags in the wrong place or lack of inline tags
...
Inline tags can contain text formatting and file structure information, and also custom variables. While they generally can be moved to fit the translation, it is also possible to put them in the wrong place. Misplacing inline tags can cause target file generation to fail.
...
| Note |
|---|
IMPORTANT! If the message does not guide you to what is 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 it. If the target file still has the same problem, you should also check if any inlines are in the wrong place and try again. |
Target is generated but it will not open: inline tags in the wrong place
If inline tags are put in the wrong place, this can also cause the generated target to have incorrect formatting, for some parts to be missing, or for the target to not open at all, and an error is generated.
...
Deselect all checkboxes except for the one in the 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.
Open the file in XTM Workbench in "Edit" mode.
Run the QA function for the document, to show only segments with warnings:
...
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. As you can see in the screenshot below, {2} tags are nested within {1}.
...
This is especially common in DOCX files, in which case the error below occurs when the user attempts to open the file:
...
If the file has been generated correctly after inline tag placement was corrected, it might be good to revert the QA check to the previous unmodified file (in the same place as before):
...
Target generates ceaselessly: stuck queues
...
It is most likely that the problem is caused by a stuck queue. The target file generation "cogwheel" will then spin endlessly without any error or other system message. In the vast majority of cases, the problem occurs during peak hours across Cloud-based clients who share common queues for different XTM modules modules.
...
URL you are using to log into XTM,
Company name you are using to log into XTM,
Project name or its ID,
Affected file name,
Affected target language.
Target does not generate at all: problem with headers
There is an error while generating the target file which might indicate that the problem is with headers. If so, the following error message is displayed after you select the red exclamation mark icon:
...
In the latter case, open a ticket to the XTM International Support team, including the XTM Workbench instance ID for the affected file in the ticket details (see How to obtain XTM Workbench URL (XTM Workbench instance ID) for help).
Target does not generate at all: issue with configuration
Sometimes, during the work progress on a project, the configuration that is used for a project might get changed (i.e a config file gets removed), and it can create an error with target generation (usually if the reversor is changed). The error message generated after the attempt to generate the target is then long and difficult to understand.
Solution: In such a case, create a support ticket for the XTM International Support team and provide all the details needed for investigation.
Target for an Excel file does not generate at all: data validation field length exceeds 255 characters
During the attempt to generate a target Excel file, you might come across the following, rather enigmatic, error message in the XTM Cloud UI: Could not obtain data.
...