RE: [xliff-inline] XLIFF Inline Markup Subcommittee Teleconference - Dec-13-2011 - Summary

[Yves Savourel <ysavourel@enlaso.com>]

Hi Andrew, Bryan, all,

> Case 2 (10 percent), an inline starts in one segment 
> and ends in a different segment
> <sc>/<ec> is good. <pc> is less good because it adds 
> complexity (extra attributes representing start and 
> end are ugly).

Just to be clear:

I'm for including <pc>, but it's important to underline that it cannot represent broken span-like codes at all. So in your case 2 here <pc> is not "less good" it's just not possible.

Or I'm missing something.

Here is a span-like code with <pc>:

<segment>
 <source>First <pc id='1'>part. Second part.</pc></source>
</segment>

We cannot do something like this:

<segment>
 <source>First <pc id='1'/>part. </source>
</segment>
<segment>
 <source>Second part.<pc id='1'/></source>
</segment>

So how <pc> could represent such non-well-formed span?
(just trying to be sure we are all on the same page)

-yves



-yves