- From: Yves Savourel <ysavourel@enlaso.com>
- Date: Fri, 6 Sep 2013 06:55:35 +0200
- To: <public-i18n-its-ig@w3.org>
Hi Felix, Dave, David, all, > - external resource ref still has a "todo". I tried to add > one and run into an issue: what if one element like "video" has > two external resouces (poster and src attributes): generate > two trans-units? I think we could use a list of IRI for the XLIFF representation. The element <video> being one of the phrasing element it would be mapped to an XLIFF inline code: <video height=360 poster=video-image.png src=http://www.example.com/video/v2.mp width=640> would be: <x id='1' itsx:externalResourceRefs="video-image.png http://www.example.com/video/v2.mp"/> Note the 's' in externalResourceRefs. One question too: can we use a space for separator? The example 68 of the specification, from which the example above was taken, has one more issue. The <video> element has a <p> element, because it's apparently also a Flow element. This causes some headache for extraction: <video><p></p></video> has currently no defined behavior: It cannot be treated as normal inline because it contains a <p>. One can make the content of <p> a nested trans-unit, but that is not specified anywhere, so another equally valid option is to have <video> split into two separated isolated trans-units with the trans-unit for <p> in-between. Cheers, -ys
Received on Friday, 6 September 2013 04:57:47 UTC