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] Translating XLIFF 1.2

> -----Original Message-----
> From: Yves Savourel [mailto:ysavourel@translate.com]
> Sent: Tuesday, February 23, 2010 3:09 AM
> To: xliff@lists.oasis-open.org
> Subject: RE: [xliff] Translating XLIFF 1.2
> Segmentation can certainly be done before the XLIFF file is created:
> XLIFF is just a file format. You just have to code it using <seg-
> source> to be interoperable.
> If a tool generates code where each <source> is an actual segment and
> does not uses <seg-source> to indicates that, it is still valid and
> following the specification, but it is simply not segmented from the
> view point of XLIFF. It's also sad because other tools won't be able to
> do much as far as manipulating segments in that file.

Are you saying that tools that require <seg-source> are unable to add it? 

You said that segmentation belongs to translation domain, so a translation tool that receives what you call an "unsegmented" file should be able to "segment" it by adding those <seg-source> you consider required for interoperability.

If tools that use XLIFF 1.2 segmentation cannot segment an unsegmented document, then something is wrong and it's indeed a sad situation.

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]