SubFlows and inline codes

[Ryan King <ryanki@microsoft.com>]

Hi TC folks,

 

We’ve been working on an XLIFF 2.0 object model and came across some questions about subFlows and inline codes. It seems to me that the example for subFlows in the 2.0 spec is incomplete, specifically this example in section 4.7.4 Sub-Flow:

 

Click to start: <img title="Start button"

 src="" alt="Click here to start!"/>

 

<unit id="1">

<segment>

  <source>Start button</source>

</segment>

</unit>

<unit id="2">

<segment>

  <source>Click here to start!</source>

</segment>

</unit>

<unit id="3">

<segment>

  <source>Click to start: <ph id="1" subFlows="1 2"/></source>

</segment>

</unit>

 

Where is <img> meant to be encoded in this example? It seems the more complete example should be:

 

<unit id="1">

<segment>

  <source>Start button</source>

</segment>

</unit>

<unit id="2">

<segment>

  <source>Click here to start!</source>

</segment>

</unit>

<unit id="3">

<originalData>

  <data id="1">&lt;img title="Start button" src="" alt="Click here to start!"/&gt;<data>

</originalData>

<segment>

  <source>Click to start: <ph id="1" dataRef="1"/><ph id="2" subFlows="1 2"/></source>

</segment>

</unit>

 

Can TC folks verify that this is the correct implementation?

 

Additionally, we have some questions around merge. I assume that there is implicit ordering based in the order of the @subFlow values and the unit id. Meaning, I know u=u1 should come before u=u2. However, how do I know that u=u1 refers to @title and u=u2 refers to @alt, and not @title and @src, or @src and @alt, when there is no id/ref mechanism for the original data attributes?

 

Thanks,

Ryan