RE: [xliff] Using XLIFF 1.2 segmentation model

Good questions. And yes, it shows that <seg-source> is not perfect (like other solutions for segmentation in 1.2 that would keep <source> backward compatible), but that does not change the fact that it is the only segmentation representation in XLIFF 1.2.

I'm looking forward to the 2.0 solutions.

Cheers,
-ys

-----Original Message-----
From: Rodolfo M. Raya [mailto:] 
Sent: Tuesday, February 23, 2010 9:26 AM
To: 
Subject: [xliff] Using XLIFF 1.2 segmentation model

Hi,

Using the optional segmentation model introduced in XLIFF 1.2 generates these problems when <seg-source> contains more than one segment:

- Cannot associate a <note> element with the corresponding segment.

- Cannot set the "translate" attribute for an individual segment as can be done with <trans-unit>.

- The "approved" status cannot be set for an individual segment as can be done with <trans-unit>..

- The translation "state" and "state-qualifier" cannot be set for an individual segment as can be done when <target> contains the translation of a unique segment.

What are the official solutions provided by the XLIFF 1.2 specification?

Regards,
Rodolfo
--
Rodolfo M. Raya   <>
Maxprograms      http://www.maxprograms.com




---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php