FW: [xliff-inline] Representing information for the starting/ending/standalone parts

From
Bryan Schnabel
Date
2011-10-08T22:42:00+00:00
ID
Thread
FW: [xliff-inline] Representing information for the starting/ending/standalone parts
Hi Yves,  I really understand what you're saying. I just have three short comments:  1) > > (1) <sc>/<ec> alone or > > (2) both <sc>/<ec> and <pc>? > > . . . or (I thought I heard) (3) <pc> alone with attributes to also >
> carry the load of <sc>/<ec>
> There is no option (3). We cannot represent spans segmented at the
> middle with <pc>...</pc> no matter what attributes it would carries.  Exactly! I think we've gone the long way around to make my point. <pc> can be made to work across spanned  segments with proper attributes (example will follow). But using <pc> across segments is as (in my opinion) ill-suited as using <sc>/<ec> in a single segment.  I could do this:  <p>These skis are good in <slang> Crud. Powder and packed powder</slang> would be better served by another ski.</p> = <seg>These skis are good in <pc fuct='start' id='s1' /> Crud.</seg> <seg>Powder and packed powder<pc fuct='end' idref='s1' /> would be better served by another ski</seg>  Okay, so I've gone out of my way to com up with a silly example, but I only