XLIFF, workflows and comments

["Rodolfo M. Raya" <rmraya@heartsome.net>]

Hi All,

Here are some links to XLIFF-related material. 

What Is XLIFF and Why Should I Use It?
by Peter Reynolds and Tony Jewtushenko
http://xml.sys-con.com/read/121957_1.htm

The key picture in this article is this:

---

Internationalization: Implementing the XLIFF Standard
by Jon Allen - PowerPoint presentation 
http://web.princeton.edu/sites/isapps/jasig/2003summerWestminster/presentations/XLIFF%20IM030610.ppt

This presentation describes a workflow based on ANT and XSL stylesheets for converting XML documents to XLIFF.

---

An Introduction to XLIFF
by Tony Jewtushenko - PowerPoint presentation 
http://www.igniteweb.org/documents/xliff_12_detailedintro.ppt

This presentation focus on the importance of XLIFF mostly, but has a section called "The real World", starting on slide 54 with details on workflows based on XLIFF.

---

Andrzej's presentation includes details on how to embed xml:tm namespace into DITA documents and how to use the extra data in the translation process. If you remove all process steps that involve xml:tm from the presentation you get a simpler picture similar to the one above.

As I said, it is not necessary to use xml:tm in the translation process if the workflow includes a good TM engine somewhere. There are advantages on using xml:tm, but end users should balance the pros and cons, not the DITA TC.

Andrzj is also right when he says that a CMS is useful for handling DITA documents, if not essential in large projects. However, using xml:tm may require a CMS as complement. From recent threads on the dita-user mailing list at Yahoo! I have the feeling that most users don't work with a CMS. This is something that should be seriously considered.

Best regards,
Rodolfo

--
The information in this e-mail is intended strictly for the addressee, without prejudices, as a confidential document. Should it reach you, not being the addressee, it is not to be made accessible to any other unauthorised person or copied, distributed or disclosed to any other third party as this would constitute an unlawful act under certain circumstances, unless prior approval is given for its transmission. The content of this e-mail is solely that of the sender and not necessarily that of Heartsome.