Tips and Tricks

Warning Messages in Memsource

Unlike errors, 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.
    Some difficulties can arise when importing Word documents that contain fields. To translate them, replace the fields with text and re-import the file into Memsource. Please see the article on field warnings for more information.
     
  • There are embedded objects within the document that have not been imported. Please see our article on embedded object warnings for details.
     
  • Job(s) ## exported with a warning (Marks reordered). Click here to download.
    In the course of translation, the document has become invalid (that is, 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.
     
  • The file contains incorrectly locked tags. Modifying/adding locked tags may result in the SDLXLIFF becoming invalid.
    SDL Studio allows users to lock segments and 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 technical process that takes place when opening files in the Studio. This warning has been added to notify users not to modify or add these tags into the translation at all. Please note that these files are best translated in the Studio—importing and translating them in Memsource is at the user’s own risk. If a user decides to translate the files in Memsource (despite the warning), tags should not be inserted into the translation.
    • How to fix a file already corrupted by the insertion of tags:
      A Quality Assurance check is in place to inform users about such malformed tags. In the segments, these can be identified visually with the 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).