Showing posts with label XLIFF:doc. Show all posts
Showing posts with label XLIFF:doc. Show all posts

Jul 7, 2013

A quick look at XLIFF:doc in memoQ 2013

memoQ 2013 introduced a few new import filters: the TMX translation import filter, which I expect will mostly find use for PEMT applications and translation memory quality assurance; the GetText PO filter, which I suspect is of limited interest unless you are one of those people who considers "xl8" and "l10n" to be in the vanguard of spelling reform; the filter and wizard for TIPP packages, an interchange format promoted by Interoperability Now! and the Linport Project; and XLIFF:doc, which has been the subject of much discussion amond the l10ners of my acquaintaince.

Despite its too-geeky company, XLIFF:doc is actually a rather interesting format. The sample I obtained showed how a document can contain content for multiple translation files, which are displayed separately in the working environment after import and, most interestingly, how file previews and terminology match information can be embedded in the XLIFF:doc file for reference.

One of the serious problems at present with memoQ's interoperability solutions for proprietary packages from other vendors is that terminology is not transferred.

If the package comes from an SDL Trados Studio user, odds are that this won't be a problem, as the majority of Trados users seem to be terrified of managing terminology with MultiTerm, and damned few of them actually do it. I was often disappointed to find that I had spent years maintaining specialist terminologies in MultiTerm for various "sophisticated" clients of mine who used Trados, only to discover one day that the data had actually never been used, because none of the client's staff dared to use MultiTerm. Of the dozen or so SDLPPX files I've been given for translation jobs in the past year or so, not one included terminology, just a bit of TM data, which transfers nicely.

STAR Transit users have a better integrated, somewhat more user-friendly terminology option and use it more often as one might expect, making it necessary to acquire this terminology in other ways for use in memoQ for now.

Using XLIFF:doc as an exchange format for translation offers a strategy for overcoming this long-standing problem. As far as I can tell, Ontram and XTM appear to be the only translation environments which generate or intend to generate XLIFF:doc as part of the Translation Interoperability Protocol packages (the TIPP packages which memoQ now imports).

Kilgray has stated no plans to generate XLIFF:doc or TIPP from memoQ projects, but I hope this changes. If all the major translation environments were to create files of these types as well as read them, we would be much, much further along with trouble-free exchange of data for projects with heterogeneous working tools.

Here's a video offering a quick "inside look" at an XLIFF:doc file imported to memoQ and the reference information (previews, terms and translation matches) it can contain: