xliff-inline — archive
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]
Teleconference - Aug-10-2010 - 13:30 UTC
Yves, on further consideration, how about we rephrase point A as:
a) to store only the XLIFF representation, discarding the native data
I think this is clearer, because it's not really that we're just discarding everything, as in the following:
Source: I like <i>italics</i>.
XLIFF: I like italics.
But rather going for something like this:
XLIFF: I like <XLIFFtagOfSomeSort/>italics<XLIFFtagOfSomeSort/>.
The existing text could imply the former as well as the latter possibility.
-Arle
On 8/10/10 10:51 AM, sic scripsit Yves Savourel:Requirement #12: (was #10, #11, and #12) After discussion, the three requirements related to the representation of the native data were grouped into a single one (#12), with the following wording: [ There must be three ways to deal with the native data corresponding to an XLIFF inline code: a) not to store it at all b) to store it along with its XLIFF representation c) to store a pointer to it along with its XLIFF representation ]
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]