The XLIFF File Lacks Content.

XLIFF files used for translation must follow specific file format and context rules in order for the translation to occur (see XLIFF Files).

One of these rules is: The XLIFF File Must Contain Translatable Content.

An XLIFF file may contain content to translate from more than one document. Those documents are separated within the XLIFF file by XML nodes inside the file (one node per document). As an XLIFF file may contain more than one of those nodes, at least one node must contain content to translate to prevent an error in Wordbee Translator.

Received Error

If you are attempting to translate an XLIFF file that does not contain translatable content, the following error message will be received:

"The xliff file node 'messages2' does not contain content to translate.”

The provided error message will be similar to the one above; however, 'messages2' will vary, as it is based on the file being used for translation and specific Wordbee Translator context settings.

Explanation

An XLIFF file may be composed of texts coming from multiple source files. Each file is held in a “file section” inside the XLIFF file. Wordbee Translator expects that the XLIFF file to have at least one file section containing translatable content. If the XLIFF file does not contain translatable content, the system will not be able to process it.

Here is how a file section looks like when it has translatable content:

XLIFF with Content

CODE

<file target-language="fr" source-language="en" datatype="plaintext" original="messages2" date="2011-10-18T18:20:51Z" product-name="my-ext">
        <header/>
        <body>
                <trans-unit id="headerComment" xml:space="preserve">
                        <source>The default Header Comment.</source>
                </trans-unit>
                <trans-unit id="generator" xml:space="preserve">
                        <source>The "Generator" Meta Tag.</source>
                </trans-unit>
        </body>
</file>

Here is an empty file section:

XLIFF - No Content

CODE

<file target-language="en" source-language="fr" datatype="plaintext" original="messages2" date="2011-10-18T18:20:51Z" product-name="my-ext">
</file>

The file node name is obtained from the “original” attribute of the “file” tag (this attribute holds the name of the original file).

Fixing the Problem

There are two ways to fix this problem and ensure that the XLIFF file can be translated, either:

Add content to the current XLIFF file.
Use another XLIFF file containing translatable content.