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] Uniqueness of language pair


Translation packages and XLIFF documents are two different things.

A package could be multilingual, have Dolby Surround sound, subtitles and 3D images. That's not an obstacle for XLIFF being just bilingual.

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

> -----Original Message-----
> From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf
> Of Yves Savourel
> Sent: Friday, January 06, 2012 1:50 AM
> To: xliff@lists.oasis-open.org
> Subject: RE: [xliff] Uniqueness of language pair
> > Even Wordbee suggested the construct only for the purpose of bulk
> > project exchange and would not consider it seriously for translating.
> I think multilingual translation packages can be handled at the package level.
> There are efforts with Linport and Interoperability Now to get some
> standardized package format done. Those could be easily made of several
> sets of bilingual XLIFF.
> The drawback: source is duplicated in different places: that make sense to
> me as the package will get eventually split into smaller parts for bilingual work
> anyway.
> In other words: XLIFF should provide a relatively small granularity: bilingual
> files are what translators are using. Then, if needed, XLIFF documents can be
> combined for larger purposes.
> Cheers,
> -ys
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: xliff-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: xliff-help@lists.oasis-open.org

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