Requirements for translated XLIFF files

Original attribute on file tag must match source
All XLIFF files contain a <file> tag like this:

<file original="example.html" source-language="en-us" datatype="html" target-language="es">

The original attribute must be the same in the source file and translated file. This check is to designed make sure the correct translation is delivered for a source file.

Ensure XLIFFS are valid XML and valid XLIFF

Uploaded XLIFFs must be valid XML and valid XLIFF documents as defined here: http://docs.oasis-open.org/xliff/xliff-core/xliff-core.html


Source and Translation must have the same trans-unit tags

A translation unit in an XLIFF file is represented like this:

<trans-unit id="tu12" resname="FORM__1232____fc__SUBMIT_LABEL">

Cloudwords identifies these translation units by id and resname (if present). All translation units from the source file must be present in the translated file, in the same order.

All translation units must have translations
Using the same example as before:

<trans-unit id="tu12" resname="FORM__1232____fc__SUBMIT_LABEL">
<source xml:lang="en-us">Request Report</source>
<target state="final" xml:lang="es">Solicitar informe</target>
</trans-unit>

Each trans-unit must have exactly one target tag.


Use the correct language code
In an XLIFF file, the target language is declared in 2 places. At least one of these must be present in the translated file.

The file tag:

<file original="example.html" source-language="en-us" datatype="html" target-language="es">

Or the target tag:

<target state="final" xml:lang="es">Solicitar informe</target>

At least one of these declarations must be present, and it must match the language that is being uploaded. If multiple declarations are present, they must have equal values.

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.