← Prev in month ← Prev in thread
Next in thread → Next in month →

XLIFF 2.1 csprd01: Best practices for Merger to handle segmentation

From
Ján Husarčík <>
Date
2016-11-16T12:30:24+00:00
ID
CAHi6kL0E9N70rzCZpfThXxomS-ZjcKC=
Thread
XLIFF 2.1 csprd01: Best practices for Merger to handle segmentation
Hello,

could you please add a note suggesting the best way how can the Merger approach modified segmentation within <unit>? E.g. "join all the segments and ignorables".

It is also unclear, how Merger should handle following valid xliff file:

<?xml version="1.0" encoding="utf-8"?>
<xliff xmlns:mda="urn:oasis:names:tc:xliff:metadata:2.0" xmlns="urn:oasis:names:tc:xliff:document:2.0" srcLang="en-US" trgLang="fr-FR" version="2.0" >
    <file id="1">
        <group id="content">
            <unit id="1">
                <segment state="final">
                    <source>1</source>
                    <target>1</target>
                </segment>
                <ignorable>
                    <source>some code snippet</source>
                </ignorable>
                <segment state="final">
                    <source>2</source>
                    <target>2</target>
                </segment>
            </unit>
        </group>
    </file>
</xliff>

If <ignorable> is not required to have <target>, it could be explicitly stated that Merger should not expect it and still correctly process the input.

Thanks,

Jan
← Prev in month ← Prev in thread
Next in thread → Next in month →