RE: [xliff] Requirements for <sc> and <ec>

Hi Rodolfo,

I just added <xliff><file> to the example â as below

<?xml version="1.0" encoding="UTF-8"?>

<source><sc id="1" type="fmt" subType="xlf:b"/>First sentence. </source>

</segment>

<source>Second sentence.<ec startRef="1" type="fmt" subType="xlf:b"/></source>

</segment>

</unit>

</file>

</xliff>

-Yoshito

From: xliff@lists.oasis-open.org <xliff@lists.oasis-open.org> on behalf of Rodolfo M. Raya <rmraya@maxprograms.com>
Date: Tuesday, April 26, 2022 at 3:41 PM
To: xliff@lists.oasis-open.org <xliff@lists.oasis-open.org>
Subject: [EXTERNAL] RE: [xliff] Requirements for <sc> and <ec>

Hello Yoshito, Can you send me the file that you tested with the validation service? The section on <sc> and <ec> elements needs to be re-written. It is not clear at all. Regards, Rodolfo -- Rodolfo M. Raya Maxprograms â â â â â â â â

ZjQcmQRYFpfptBannerStart

This Message Is From an External Sender

This message came from outside your organization.

ZjQcmQRYFpfptBannerEnd

Hello Yoshito,

Can you send me the file that you tested with the validation service?

The section on <sc> and <ec> elements needs to be re-written. It is not clear at all.

Regards,

Rodolfo

--
Rodolfo M. Raya
Maxprograms http://www.maxprograms.com

-------- Original Message --------
Subject: [xliff] Requirements for <sc> and <ec>
From: Yoshito Umaoka <yoshito_umaoka@us.ibm.com>
Date: Tue, April 26, 2022 4:08 pm
To: "xliff@lists.oasis-open.org" <xliff@lists.oasis-open.org>

Dear XLIFF experts,

I was looking at some issues related to <sc>/<ec> handling and reading XLIFF 2.1 specification closely.

The attribute isolated MUST be set to yes if and only if the <ec> element corresponding to this start marker is not in the same <unit>, and set to no otherwise.

If there are <sc> and corresponding <ec> are in a same <unit>, then it's NOT isolated. It looks this statement is very straight forward, but it becomes ambiguous if this constraint also applies to <target>.

The example in this section is below ?

<unit id="1">

<segment>

    <source><sc id="1" type="fmt" subType="xlf:b"/>

        First sentence. </source>

</segment>

<segment>

    <source>Second sentence.<ec startRef="1" type="fmt"

        subType="xlf:b"/></source>

</segment>

</unit>

But the spec is not clear about the case when only one segment has translation available.

<unit id="1">

<segment state="translated">

  <source><sc id="1" type="fmt" subType="xlf:b"/>

        First sentence. </source>

  <target><sc id="1" type="fmt" subtype="xlf:b"/>

        æåãæã</target>

</segment>

<segment>

    <source>Second sentence.<ec startRef="1" type="fmt"

        subType="xlf:b"/></source>

</segment>

</unit>

Does above valid? When translation memory is managed at each parsed segment level, then this could happen. I think the constraints should only apply to <source> part, otherwise, a single unit cannot be partially translated.

BTW, I wanted to check if the XLIFF is validated with the XLIFF Validation Service. I found the example in the XLIFF specification was invalidated with the message: Reason: <sc> element without matching <ec> in <source>. Rodolfo, you might want to look at this.

-Yoshito

--------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php

xliff message