| Table of Contents |
|---|
...
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:
...
It is associated with the Initialization error in XTM Workbench (see XTM Workbench – most common issues & troubleshooting).
Solution: As stated in the referenced article, the above issue stems from “deserialization" of files' headers on the back-end side of XTM, which gives two solutions to the problem:
...
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
...
See an official, helpful tutorial on how to correctly set up a cell range dropdown list, here: Create a dropdown list.
Target file does not contain translation from XLIFF import via API
There are some edge cases when a generated project’s target file does not contain translation content, although the translation in question is present in XTM Workbench. This issue is related to the case that the translation that is missing from the target file is actually an offline translation imported from XLIFF via API.
The root cause of this issue turned out to be quite simple: the target file generation process took place before the XLIFF file containing the offline translation was imported. The time interval between those two actions might be just a couple of milliseconds.
As an example, the process for generating the target file ended at 19:02:56,938. However, the process for the XLIFF file import ended at 19:02:57,784.
Taking the foregoing into account, the target file was generated less than one second before the process that was responsible for importing translations from the uploaded file finished its work.
Solution: If actions are being performed with some automation and API usage, you can add some extra time between an XLIFF upload action and target file generation (add some sleep()). This will enable you to ensure that a similar situation will not happen in the future.