Re: XLIFF Mapping - status

Sorry to resurrect an old thread. I have two comments on the document-
First, is "itsx" a prefix for another namespace besides the one that
"itsxlf" represents?
Second, I think that "targetLocaleRule" was supposed to be
"targetPointerRule".

I am starting the XLIFF->HTML conversion task of WICS, so I may come up
with lots of questions. Starting in a few moments...

Nathan


On Thu, Sep 5, 2013 at 9:55 PM, Yves Savourel <ysavourel@enlaso.com> wrote:

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