When you import an XLIFF file into Easyling, you will eventually get an email signifying the end of the import process and that your content is now in the database. However, things are not always so smooth, and you may get an email notifying you of an error in the import process that caused it to fail, or skip segments. There can be many reasons for this.
Some version of Trados tends to create an SDLXLIFF file upon exporting the translation. In this case, simply use the "Finalize" batch task or open the document in the Editor, press SHIFT+F12 and select the target file location. This will create the XLIFF file for you (instead of SDLXLIFF). There may also be a need to disable segment info storage in Trados (Options -> File Types -> XLIFF -> Settings -> 'Do not store segmentation information in the translated file' should be checked). This may require creating a new project.
Maybe the single most common reason is an illegal character in the XLIFF. This is usually denoted by the "Illegal character" error message in the email, followed by a line and column number where you can find the illegal character in the file.
The reason for this is usually a coding mismatch: all our XLIFF files are exported using the world-standard UTF-8 codepage. However, your CAT tool may save the file using another codepage, depending on the language, which may cause certain characters to appear as invalid. This can be easily verified by opening the XLIFF in, say, Notepad, or any text editor, and looking at the character at the described coordinates. Boxes or other nonsensical symbols mean that the codepage is wrong. If you see this, you need to check your CAT tool's settings to see if the file is indeed exported using UTF-8, and if it isn't, you need to re-export the file using it, after which you'll be able to import it without further problems.
A second cause can be tagging issues: sometimes, CAT tools remove some of the XLIFF tags, and the result is a syntactically invalid XML document (the opening and closing tags are imbalanced). During import, this causes an error in our parser, which results in a skipped entry (previously, it resulted in a failed import entirely, but we upgraded the import subsystem to work around this, and now we only skip that given segment). This is a stealthier error, however, in that the most usual indication of it is that segments are "missing" from the translated site, even though they were translated before, but it can be verified by carefully examining the entry in the XLIFF visually (this is a somewhat more technical task, a text editor with syntax highlighting is recommended, or simply contact us at support@easy-removethis-ling.com - in which case, please include the file you tried to upload, and try to contact us within 12 hours, before the incident is pushed out of our server logs). In this case, sometimes, re-exporting the translation from the CAT tool after checking the settings helps, but most often, it results in a similar error. Either we insert the the translations for you, or you'll have to copy them through the Workbench (which takes care of ensuring the tags are in place, so you don't have to worry about them).
0 Comments