Best way to mark up an image in XLIFF 2.0?

["Schnabel, Bryan S" <bryan.s.schnabel@tektronix.com>]

Hello,

 

I looked at the current specification to see how we say images should be represented in XLIFF 2.0. The only reference I see is in sub-flows:

 

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>

 

This is all great. But I do not see a recommendation for storing the src="" information.

 

Suppose a skeleton is not to be used.  

 

Let’s consider a more simple case where no sub-flow information is in play, and let’s say the source is well-formed, spanning code. And we want to choose the most XML-friendly way.

 

So our choice is to not use <sc>, <ec>, but rather to use <pc>.

 

<p>This is a test <img src="" /></p>

 

I wonder if we need to add “x-“ extensibility to inline elements? Or, would we recommend something like this:

 

  <unit id="t1">

   <segment>

    <source>This is a test <pc id="img.1" type="image"> big-happy-smile.jpg</pc></source>

    <target>This is a test <pc id="img.1" type="image"> big-happy-smile.jpg</pc></target>

   </segment>

  </unit>

 

If that sample is legal, would we also need to add a lock=”yes”, or something since the content of <pc> could accidentally translated?

 

I need to know this to provide a robust answer to Yves’ question about the fs attribute.

 

Thanks,

 

Bryan