Re: [xliff] subState when joining segments

Hello Yves,

I believe that it is up to the owner of the subState state machine to define behavior on resegmentation in addition to the state behavior on resegmentation.

IMHO the first case you list is an update that is covered by the PRs tying state and subState, if you do not know to what subState is to be updated you simply drop it.

In the other case, I believe it should be dropped as well, unless you know the privately defined behavior, this probably needs a clarifying note.

The baseline is that the core should not even attempt to prescribe handling of private sub* values, neither here nor anywhere else in the spec.

Cheers

Dr. David Filip

=======================

LRC | CNGL | LT-Web | CSIS

University of Limerick, Ireland

telephone: +353-6120-2781

cellphone: +353-86-0222-158

facsimile: +353-6120-2734

mailto: david.filip@ul.ie

On Mon, Nov 4, 2013 at 12:49 AM, Yves Savourel <ysavourel@enlaso.com> wrote:

Hi all,

While trying to implement joining segments I ran into an issue not addressed in the processing requirements of the Segmentation
Modification section:

There is no guideline on how to handle subState if it has different values in the two original segments.

A first solution would be to take the subState value associated with the state value that is used in the resulting segment. So if we
have this:

<unit id="1">
<segment id="s1" state="reviewed" subState="my:value1">
<source>Sentence 1. </source>
<target>Phrase 1. </target>
</segment>
<segment id="s2" state="translated" subState="my:value2">
<source>Sentence 2.</source>
<target>Phrase 2.</target>
</segment>
</unit>

We would get this:

<unit id="1">
<segment id="s1" state="translated" subState="my:value2">
<source>Sentence 1. Sentence 2.</source>
<target>Phrase 1. Phrase 2.</target>
</segment>
</unit>

But that breaks down if we have no difference between state values and differences between subState values. For example with this:

<unit id="1">
<segment id="s1" state="initial" subState="my:value1">
<source>Sentence 1. </source>
</segment>
<segment id="s2" state="initial" subState="my:value2">
<source>Sentence 2.</source>
</segment>
</unit>

We would get this:

<unit id="1">
<segment id="s1" state="initial"
subState="???my:value1 or my:value2"???>
<source>Sentence 1. Sentence 2.</source>
</segment>
</unit>

One possible option would be to take the value that has the value string (i.e. the part after the prefix) with lowest rank in
alphabetical order. This would allow user to define their set of values accordingly.

Thoughts?
-yves

---------------------------------------------------------------------
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