OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

xliff message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: [xliff] Simplified XLIFF element tree

> -----Original Message-----
> From: Asgeir Frimannsson [mailto:asgeirf@redhat.com]
> Sent: Tuesday, August 24, 2010 5:45 AM
> To: xliff
> Subject: Re: [xliff] Simplified XLIFF element tree
> Hi Andrzej,
> From my perspective, a richer segment and structural separation can lead to
> a better and richer interoperability between XLIFF and xml:tm, where the
> typical XLIFF "extraction unit" is a tm:te and a segment is a tm:tu.
> I think a valid goal for all of this is
> (1) to have a single representation for segmented content within XLIFF 2.0,
> and
> (2) to ensure that the representation of segmentation that happens post-
> extraction is the same representation as one that happens in the extraction
> process.

Hi Asgeir,

I agree with your goals. There should be one representation for segmented content, which could very well be a traditional <trans-unit> with a <source>/<target> pair.

The 2nd goal can be achieved by keeping the optional unsegmented text separate from the segmented version. In other words, separate from the traditional <trans-unit> that could be used for the first goal.

Rodolfo M. Raya   <rmraya@maxprograms.com>
Maxprograms      http://www.maxprograms.com

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]