RE: ITS to XLIFF conversion and roundtripping

Hi Felix,

> I have worked on ITS to XLIFF conversion and roundtripping, see
> http://www.w3.org/International/its/wiki/ITS_Translate_Decorator#XLIFF_generation_and_roundtripping
> There is still a lot to do, but this might be enough so that 
> people can play with it. I'm looking forward esp. towards feedback 
> about the XLIFF format.

A few notes, just looking at the example current XLIFF document generated.
(I'm guessing some of the issues are just because it's a prototype, but I'll mentionned them just in case):

1) I see:

<xl:pbt id="d1e13_start2"><code itd:id="d1e13" itsTve="no"></xl:pbt>
<xl:ph id="d1e13_notrans_content2">un-translatable code 2</xl:ph>
<xl:pbt id="d1e13_end2"></code></xl:pbt>

Shouldn't more like ethis:

<xl:bpt id="d1e132"><code itd:id="d1e13" itsTve="no"></xl:bpt>
<xl:ph id="d1e13_notrans_content2">un-translatable code 2</xl:ph>
<xl:ept id="d1e13"></code></xl:ept>

(bpt=begin-paired-tag, ept=end-paired-tag)
 

2) I see:

<xl:ph id="d1e19_notrans_content1">
un-translatable 
<xl:pbt id="d1e21_start1"><code itd:id="d1e21" itsTve="no"></xl:pbt>
<xl:ph id="d1e21_notrans_content1">code 3</xl:ph>
<xl:pbt id="d1e21_end1"></code></xl:pbt>
</xl:ph>

I've never seen a <ph> element to include any other element (except a <sub> with text in it). From the specification
(http://docs.oasis-open.org/xliff/v1.2/os/xliff-core.html#ph) and the schema I don't think it's valid to have the other XLIFF tags
within the <ph>.


That's all for now.
-yves

Received on Thursday, 3 July 2008 16:39:14 UTC