RE: [xliff] XLIFF 2.0 Core

["Schnabel, Bryan S" <bryan.s.schnabel@tektronix.com>]

And if my memory is correct, I believe Magnus told me Trados uses XLIFF as its internal storage format. Am I remembering correctly Andrew?

- Bryan
________________________________________
From: Rodolfo M. Raya [rmraya@maxprograms.com]
Sent: Friday, April 08, 2011 5:42 AM
To: xliff@lists.oasis-open.org
Subject: RE: [xliff] XLIFF 2.0 Core

> -----Original Message-----
> From: Yves Savourel [mailto:ysavourel@translate.com]
> Sent: Friday, April 08, 2011 9:11 AM
> To: xliff@lists.oasis-open.org
> Subject: RE: [xliff] XLIFF 2.0 Core

Hi Yves,


> > It is my understanding that XLIFF can be used in these situations:
> > 1. A format that product development can create to provide
> > translatable text to be translated.
> > 2. A format that can be used within a tool set to manage the
> > translation of the content.
> > 3. A format that one tool set can export which would then be
> > imported into another set of tools.
>
> I'm not sure #2 applies. If they keep their data within a unique toolset there
> is little advantage in using anything but some proprietary format it would
> seems. They only reason would if they want to be ready for #3.

I use XLIFF format to keep the data used by my translation tools. That's case #2 in David's list.

By using XLIFF as internal data format, there is no need to export/import anything for exchanging data with another tool (case #3), the data is ready to use.

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



---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php