Preparing Translation Bundles

If you are working with a translator who is using a third-party tool—such as Trados or memoQ—you first need to package your Lingo project in order to separate the necessary files for the translator. You can then send the bundle (which is a ZIP file or LIPRJZIP file) to the translator. This file consists of the content files requiring translation.

How to Prepare a Bundle

1. Select View > File List.

   Note You can also create bundles from the TOC View window pane. See TOC View Window Pane.

2. Select the files to be included in the bundle. You can hold the SHIFT key to select a range, or you can hold the CTRL key to select individual items. Selecting multiple files can be done only if you are in grid view.
3. In the local toolbar click the Create Bundle button .

4. In the Bundle Settings area, select the file type for the bundle and the project files to include with the bundle.

   • Lingo Project Bundle Packages the bundle as an LIPRJZIP file to send to a translator who also uses Lingo.
   • XLIFF Files Bundle Packages the bundle as a ZIP file to send to a translator who uses another third-party tool, such as SDL Trados or memoQ.

   • Language (Optional) Select the target language for the files in the bundle. You can select an individual language or all languages.

     

     Note You will only see this option if you are working with a multilingual project.

     Note If you need to send multiple languages to the translator, you can send each language as individual bundles, or you can select All languages to send all of the files in one bundle.

     Note You cannot add or remove languages to a project while a bundle is out for translation. You must import the returned bundle before you can add or remove languages. See Bundles.

   • Include Project Translation Memories Includes the project's translation memories (TMs) with the bundle.

   • Include Project Termbases Includes the project's termbases with the bundle.

     Example  

     You are bundling a large Lingo project for translation. The project is already partially translated, but you are using a new translator to finish the project. By including the connected translation memories and termbases with the bundle, the new translator can use the previous translator's completed work (using the translation memory), as well as any standards for commonly used terms that you may have established with the previous translator (using the termbase). This saves you time because you won't need to review these things with the new translator, and it saves you money because the new translator will not need to retranslate segments that have already been completed.

5. (Optional) In the Bundle Files area, you can use the filters to search for additional files to include with the bundle. You can filter by file type, translation status, and difference status. Any project files not yet included in the bundle and that match your selected filters display in the Project Files grid. Any files currently included in the bundle display in the Output Files grid.

   Note The filters available in your bundle depend on the files available in your project. For example, if you do not have any new files in your project, you will not see the New difference status filter. If you add new files to the project, the New filter becomes available.

   Note If you have already filtered your project using target or condition filters, the available files reflect the filters you applied. You can only bundle files that are part of your current project. See Dynamic Filtering.

   Example  

   You have already sent your project to your translator to begin translating content. After a few weeks, you need to make a major, unexpected change to a section of the documentation that you have already sent for translation. Rather than sending the whole project to the translator again, you can use the project files filters to send only the changed files to the translator.

   After updating your project in Lingo (see Updating Projects), create a new bundle and use the project files filter to locate files with a difference status of Different. Any files you changed display in the Project Files grid. Select the files to include them in the bundle.

   

6. Click OK. The project is scanned and computed statistics for the project are shown (if you have TM installed, as recommended).
7. Click Close. A Windows subfolder (within your project folder) named "Exporting" opens. This subfolder holds a ZIP file or LIPRJZIP file, depending on the bundle settings you chose. This file contains the files that your translator needs to work with.

8. Send the ZIP file or LIPRJZIP file (via email, FTP, etc.) to the translator.

   Important If you need to make changes to your bundle before you send it to the translator, you should not remove files from the ZIP or LIPRJZIP file, as this could cause problems merging the bundle back into Lingo later. Instead, it is recommended that you create a new bundle and send the corrected bundle to the translator.

What’s Next?

After receiving these files from you, the translator unzips the file, opens it in Lingo or imports the content files into a third-party tool, and translates all of the segments. When finished, the translator puts the completed files into a ZIP or LIPRJZIP file, and sends it to you. At this point, you can merge those files into your original Lingo project. See Merging Completed Bundles.