Warnings do not prevent the actual translation from taking place, but not taking warnings into account may prevent the successful export of the target document or cause the completed file to become corrupted. Below are some of the most common errors.
- The imported file contains fields. To translate them, replace the fields with text and re-import it into Memsource.
Please see this dedicated article.
- There are embedded objects within the document that have not been imported. Please see this article for details.
- Job(s) ## exported with a warning (Marks reordered). Click here to download.
In the course of translation, the document has become invalid (MXLIFF marks are present in the target document). In order to generate a correct document, the marks were replaced with marks from the source. Please check the final document to make sure no errors have been introduced to your target file.
- This file contains locked incorrectly tags. Modifying/adding the locked tags may result in the sdlxliff becoming invalid.
SDL Studio allows users to lock not only segments but also tags to prevent any changes to them. The internal handling of these tags is a property of SDL, thus we are not aware of the process that takes place when opening the file in the Studio. For this purpose, the warning has been added to warn users not to modify or add these tags into translation at all. Please note that these files are best translated in the Studio, importing and translating them in Memsource is at user’s own risk. If the user decides to translate the files in Memsource (despite the warning), the tags should not be inserted into the translation.
How to fix a file already corrupted by insertion of the tags:
A Quality Assurance check is in place to inform users about such Malformed tags. In the segments, these can be identified visually with Expand Tags option turned on. Removing these tags from the translation and exporting the file again should allow the Studio to open it correctly (without the locked tags present).