Symptom 1
In SDL Trados Studio you want to convert your translated file back to the original format. However, you get the following error message:
Failed to save target content:, hexadecimal value 0x0B, is an invalid character. Line 14, position 110.
NOTE: the values in this error message may be different. When you double click on the line in the error message to fix the problem, your cursor does not jump automatically to the correct location in your file.
Symptom 2
While opening SDL Trados Studio you receive error message:
Failed to load project 'C:\[PATH to project folder]\[project name].sdlproj'.
There is an error in XML document (XYZ,XY).
hexadecimal value 0x0B, is an invalid character. Line XYZ, XY.
Symptom 3
While opening an SDLXLIFF document you receive the error message:
Unexpected error
hexadecimal value 0x1F, is an invalid character. Line XYZ, XY.
Explanation 1: Invalid character in *.sdlxliff document/file
The error message points to an invalid XML character within the SDLXLIFF file. If you open your SDLXLIFF file in a text editor, you would find something similar to the following:
<tuv xml:lang="de-DE" >
<seg>Test the characters.</seg>
</tuv>
<tuv xml:lang="en-US">
<seg>Test the charaters</seg>
</tuv>
There are several invalid characters here that could have come from the source file and be copied to the target segment. Also, invalid characters might already be stored within a translation memory from other translations, and you applied a match in the current translation.
Further. such characters are commonly not printable and are not noticeable in an usual editor. As SDLXLIFF files are basically following the XML standards these characters are not allowed as per XML 1.0 declaration.
Explanation 2: Invalid character in *.sdlproj file
If you not already received the error while trying to save a target version, then maybe after executing a verification or at another stage. In most cases the error message is saved in the *.sdlproj
file that contains information about the project settings and error messages.
The invalid character(s) is/are stated in the error message and also saved within the *.sdlproj
file. Because the *.sdlproj
file itself is an XML document, it therefore contains an invalid character - as described in Explanation 1.