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: Wondering about sub-flows (meant NOT as a comment for PR 2)


I’m reading our specification for sub-flows. I DO NOT wish to make a comment that will impact the Public Review. But I was just wondering about best practices.

 

Our example does not mention anything about the uniqueness of <unit> IDs that are involved in a sub-flow. So I could have something like this (borrowing from our example, and adding extra <unit> elements):

 

<unit id="1">
 <segment>
  <source>Blade engagement button</source>
 </segment>
</unit>
<unit id="2">
 <segment>
  <source>Click here to engage the blades</source>
 </segment>
</unit>

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

 

 

So it is not clear if my resolved sub-flow will say:

 

Click to start: <img title="Blade engagement button"
 src="" alt="Click here to engage the blades"/>

 

Or:

 

Click to start: <img title="Start button"
 src="" alt="Click here to start!"/>

 

 

So I wonder if it would be a best practice to wrap all <unit> elements that make up a sub-flow into a <group>?



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