Académique Documents
Professionnel Documents
Culture Documents
handoff/handback guide
translating memoQ handoff packages in other tools
Contents
Contents ...................................................................................................................................... 2 1 Handoff and handback in memoQ .............................................................................................. 3 1.1 Setting up the project and distributing handoff packages ........................................................ 3 1.2 Working with a handoff package: import, process (translate), and deliver ............................. 4 1.3 Receiving the handback package on the project managers end.............................................. 4 2 Using a memoQ handoff package in other tools.......................................................................... 4 2.1 Structure of a memoQ handoff package ................................................................................... 4 2.2 Unpacking a memoQ handoff package and using its contents ................................................. 5 2.3 Packing up the translated XLIFF files in a memoQ handback package ..................................... 6 2.4 Updating the master project from translations performed in other tools ............................... 7 2.5 Troubleshooting handoff/handback problems in memoQ ....................................................... 8
This guide covers memoQ version 6.2. It contains text items from the English user interface of the program. These items are under constant verification and are subject to change without prior notification. If you are viewing this document in an electronic form for example, in Adobe Reader , web addresses are clickable, and take you to the page described in the text. This document assumes that you are familiar with the memoQ translation environment, so it does not list every step of the procedures. For more information on performing specific actions, refer to the memoQ Help, the Knowledge Base (http://kb.kilgray.com/) and/or the Resource Center (http://kilgray.com/resource-center) .
Page 2 of 8
In the project manager edition of memoQ, it is easy to create projects for teams of translators. After you create a local project, you can write a name next to each document, and then create packages or handoff packages for each translator in the project. The best tool to process handoff packages created in memoQ is memoQ itself. However, memoQ uses standard file formats when putting together the handoff package. memoQs handoff packages can be processed in other translation tools as well. This document gives a short summary of the handoff/handback workflow in memoQ, and explains how the handoff or handback packages can be disassembled in order to process their contents in other tools, or troubleshoot potential problems.
A handoff package contains the documents to translate, the necessary translation memories, term bases, and further resources (such as corpora) if there are any. memoQ will pack up all local translation memories and term bases that are added to the local project. If the project uses a memoQ serv-
Page 3 of 8
er, the handoff package also contains references to the server-based translation memories and term bases. memoQ creates one handoff package file for each project member. The files have the *.mqout extension. The project manager needs to send these files to the project members in e-mail.
1.2 Working with a handoff package: import, process (translate), and deliver
When the translator receives the handoff package (the *.mqout file), she needs to open it in memoQ. The translator needs the translator pro edition of memoQ to do that. 1. Start memoQ, and click the Import handoff package link in the Dashboard. Navigate to the *.mqout file you received from the project manager. From the contents of the handoff package, memoQ will create a new local project for you. 2. Translate the documents in the same way as you would do in a local project that you create. 3. When the documents are translated, navigate to the Translations pane of Project home, and then click the Deliver/return link below the document list. memoQ creates a handback package from the documents in the project, and saves the package in a file with the *.mqback extension. You need to e-mail this file back to the project manager. Note: The *.mqback file contains the translated documents only.
Page 4 of 8
the MQXLZ format (a zipped XLIFF format). XLIFF is a standard bilingual document format that stores all aspects of a document regardless of the format of the original source document. An XLIFF file can accommodate any types of source documents: Word documents, Excel spreadsheets, HTML files, XML files etc. From an MQXLZ file in a *.mqout package, memoQ can create the preview of the file, and it can also export the translated document. However, these documents can be translated in any translation tool that supports XLIFF documents.
TM: Contains the translation memories used in the project. The translation memories are includ-
ed in the form of TMX files. TMX is a standard exchange format for translation memories between different translation tools. Practically, any translation tool can import a translation memory from a TMX file.
TB: Contains the term bases used in the project. The term bases are saved in the CSV (comma-
separated values) format. This is not exactly standard, but it is the most generic way of storing tabular data (i.e. spreadsheets or tables). Practically, any translation tool that can manage terminology can also import term bases from such files. The handoff package can contain other subfolders too, but they are specific to memoQ, and are not very useful in other translation tools.
Page 5 of 8
4. Load the XLIFF files into your translation tool. You may have to unzip the MQXLZ file and rename the included MQXLIFF file to the XLF file extension (*.xlf). If the translation tool is project-based, create a project with the XLIFF files, and add the translation memories and term bases to the project. Note: When you want to use SDL Studio to translate the XLIFF file, you add the MQXLIFF file extension to Studios existing XLIFF filter. SDL Studio will then recognize the MQXLIFF file extension and import the file. 5. When you finish the translation, save the XLIFF files. You may need to change the file extension back to *.mqxliff, and replace the original MQXLIFF file in the MQXLZ file with this one. After this, you can pack the files up so that memoQ can treat them as a handback package. For details, see Section 2.3. Do not attempt to export the translated document in the original format. The XLIFF files contain the formatting data in a memoQ-specific form. This means that the original document format can only be reconstructed by memoQ.
The parts in italics can change from project to project. 4. In the file, change <HandoffPackageInfo to <HandoffDeliveryPackageInfo. Change <UserName to <User. 5. Save the file. 6. Create a zip file from the contents of this folder. (It should now contain the translated XLIFF files and the DeliveryPackageInfo.xml file.) If no archiving program is installed on your computer, use
Page 6 of 8
the method built into Windows: select all files in the folder, right-click, point to Send to, and then choose Compressed (zipped) folder. 7. The result will be a file with the *.zip extension. Rename the file so that it is called ProjectName.YourName.mqback. 8. Send the file to your project manager. The project manager will be able to update the master project the same way as she would when she received a handback package directly from memoQ.
2.4 Updating the master project from translations performed in other tools
If the documents in the handoff package were translated in a translation tool other than memoQ, the project manager might receive XLIFF files in the delivery. Important: If you receive a delivery package (an *.mqout file), use the standard method to update your project: go to Project home > Overview, click the Handoff/delivery tab, and then click Receive delivery. Then you can locate and select the *.mqout file you received. If the other translation tool processed the XLIFF files correctly preserving all meta-information in the XLIFF file that was originally included by memoQ , memoQ will be able to update the documents in the master project from the XLIFF files handed back. Here is how you can update the master project from XLIFF files: 1. Save the XLIFF files from the e-mail in a folder on your computer. 2. Open the master project in memoQ, and navigate to the Translations pane of Project home. 3. Below the document list, click the Import with options link. In the Open dialog, navigate to the XLIFF files you received. In case memoQ cannot identify and update the corresponding documents from the XLIFF files. However, all is not lost if memoQ cannot update them. Here are two troubleshooting tips: (1) If memoQ complains that it cannot find the corresponding documents in your project, you always have the option to add the XLIFF files to the project as new documents. You can then confirm the contents of these new documents to the primary translation memory of the project, and then use the Pre-translate command to bring the contents of the original documents up to date. You can then export the original documents which were pre-translated from the newly imported documents (which contents were saved to the primary TM). Note: If you remove the old documents from the project and only use the received back and newly imported XLIFF files, be careful when doing this: always make sure that you can export the translated document in the original format from the new documents. (2) If memoQ finds the corresponding documents but cannot update them, the best practice is to create a new project, and import the received translated XLIFF files there. Use the same primary translation memory in this project as well. Confirm the translations into the translation memory. Then, open the original master project again, and use Pre-translate to bring the document contents up to date. Alternatively, you can export the document contents from the new project as well (if the export data were preserved in the XLIFF files by the other translation tool).
Page 7 of 8
Page 8 of 8