xliff-promotion message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: <group> overloaded in XLIFF 1.2
- From: David Filip <davidf@davidf.org>
- To: xliff-promotion <xliff-promotion@lists.oasis-open.org>, Yves Savourel <ysavourel@enlaso.com>
- Date: Tue, 7 Feb 2012 18:42:14 +0000
Hi Yves,
when I was referring to the overload of <group> in 1.2 spec
I had this attribute in mind
This is also what IN! are using for merging <trans-unit>s if segmentation does not fit.
So if one of the uses of group is for merging trans-units, they cannot be blamed IMHO if they choose to use it with this semantics only. Group is an optional element that is potentially recursive but no guidance and/or processing requirements are given in the 1.2 spec, so they should be fine I guess in using it for just merging management..
Rgds
dF
PLEASE NOTE MY NEW MOBILE CONTACT!
David Filip, Ph.D.
=====================
cellphone: +353-86-0222-158
mailto:davidf@davidf.org
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]