Re: [xliff-comment] XLIFF 2.1 csprd01: Best practices for Merger to handle segmentation

[David Filip <david.filip@adaptcentre.ie>]

Thanks, Jano,

you can follow the disposition of your comment here:

https://issues.oasis-open.org/browse/XLIFF-12

We will endeavor to resolve this issue and apply the resolution by early December 2016

Any comments or disagreement with disposition of your comment please send in this thread

Cheers and thanks

dF

Dr. David Filip

===========

OASIS XLIFF OMOS TC Chair

OASIS XLIFF TC Secretary, Editor, Liaison Officer

Spokes Research Fellow

ADAPT Centre

KDEG, Trinity College Dublin

Mobile: +420-777-218-122

On Wed, Nov 16, 2016 at 12:30 PM, Ján Husarčík <jan.husarcik@gmail.com> wrote:

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