OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

xliff message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] (XLIFF-12) Best practices for Merger to handle segmentation

David Filip created XLIFF-12:

             Summary: Best practices for Merger to handle segmentation
                 Key: XLIFF-12
                 URL: https://issues.oasis-open.org/browse/XLIFF-12
             Project: OASIS XML Localisation Interchange File Format (XLIFF) TC
          Issue Type: Improvement
          Components: other
    Affects Versions: 2.1_csprd01
         Environment: http://markmail.org/thread/kqfiottjde6yxrks
            Reporter: David Filip
            Assignee: David Filip
            Priority: Minor
             Fix For: 2.1_csprd02

FROM: Ján Husarčík <jan.husarcik@gmail.com>

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>some code snippet</source>
                <segment state="final">

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

This message was sent by Atlassian JIRA

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]