OASIS Open Mailing List Archives  ·  All Lists  ·  xliff-inline  ·  2012-07

xliff-inline — archive

[Date Prev]  |  [Thread Prev]  |  [Thread Next]  |  [Date Next]   —  [Date Index]  |  [Thread Index]  |  [Month Index]  |  [List Home]

SC F2F outcome: handling split


During the face-to-face meeting there was a consensus on changing the way the <mrk> element would be represented when it is broken down by overlapping spans or by segmentation. The current draft describes a way to handle this by splitting the element into several parts. It was found a bit difficult to implement in some cases. Such notation is also rather not user-friendly, and potentially very difficult to read if you have several overlaps. The new method would use two elements: <sm/> and <em/> (working names for now) that would behave similarly to <sc>/<ec>. Example, how to add an annotation here: <pc id='1'>This <pc id='2'>is</pc> a</pc> test [________________] With the current method of duplicating <mrk>: <sc id='1'><mrk id='m1'>This </mrk><sc id='2'><mrk id='m1'>is</mrk><ec rid='2'/> a<ec rid='1'/> test With <sm> and <em>: <pc id='1'><sm id='m1'/>This <pc id='2'>is<em rid='m1'/></pc> a</pc> test - more consistent with the inline codes mechanism - possibly a lot less verbose Cheers, -ys

[Date Prev]  |  [Thread Prev]  |  [Thread Next]  |  [Date Next]   —  [Date Index]  |  [Thread Index]  |  [Month Index]  |  [List Home]