| 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:
...
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 appear in other elements (like in<menucascade>in some types of XML file). 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 will not open at all and an error will be generated.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 then not extracted for translation. The inline tags containing the information about this text style can sometimes be moved to a place where they hide the translated text as well.
...
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
...