When input XLIFF 1.2 contains multiple <target> elements invalid XML is produced

When processing XLIFF files with Okapi which contain multiple target tags in the input the output will contain invalid XML if the Okapi events are just written back to XLIFF (for example with Rainbow with a filter pipeline consisting of “Raw Document to Filter events”; “Filter events to raw document”)

The input

‌

<?xml version="1.0" encoding="utf-8"?>
<xliff version="1.2" xmlns="urn:oasis:names:tc:xliff:document:1.2">
    <file datatype="plaintext" original="something" source-language="en-US" target-language="de-DE">
        <body>
            <trans-unit id="t1">
                <source>City</source>
                <target xml:lang="de-DE">Ort</target>
                <target xml:lang="fr-FR">Ville</target>
            </trans-unit>
        </body>
    </file>
</xliff>

Becomes

<?xml version="1.0" encoding="windows-1252"?>
<xliff xmlns="urn:oasis:names:tc:xliff:document:1.2" version="1.2">
    <file datatype="plaintext" original="something" source-language="en-US" target-language="de-DE">
        <body>
            <trans-unit id="t1">
                <source>City</source>
                <target xml:lang="de-DE">Ort</target>
                <target xml:lang="fr-FR"-ERR:PROP-NOT-FOUND->Ville</target>
            </trans-unit>
        </body>
    </file>
</xliff>

A warning is generated that the property “mtConfidence” is not found.

Comments (0)