Merging Completed Bundles

After the translator returns the completed ZIP or LIPRJZIP file, you can merge its contents into your original Lingo project.

[Menu Proxy — Headings — Online — Depth3 ]

How to Merge a Completed Bundle

  1. Save the returned ZIP or LIPRJZIP file to a location on your computer.

  2. In Lingo select View > File List.

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

  3. In the local toolbar click the Merge Completed Bundle button .

  4. In the dialog find and double-click the ZIP or LIPRJZIP file that the translator returned. You may need to select the appropriate file type from the file type drop-down. Click Open. The updated files are merged with your project.

 

Note You cannot merge a bundle back into your project unless the files within it are named the same as the files in the original bundle. Additionally, the bundle must have the same folder structure as the original bundle (i.e., files must reside in the same relative locations and folders cannot have been renamed).

Note If you sent a multilingual bundle to the translator, when you merge the bundle, the files will automatically merge into the appropriate language in your project.

Note Translators must return a bundle in the same file format as the original bundle they received. If you sent the translator a Lingo project file (*.LIPRJZIP), you should receive an LIPRJZIP file back from the translator. Likewise, if you sent the translator a ZIP file, should receive a ZIP file back.

What’s Next?

Now that all of the segments in the project are translated, you can ensure the translation work is complete. You can do this in a few ways.

  • Statistics You can select File > Compute Statistics. This displays a statistics report showing detailed information for the project and each file. Using this report, the content developer can see exactly how many words and segments were translated. See Computing Statistics.
  • Reports In addition to running a statistics report, you can also run quality assurance (QA) reports to find any discrepancies between the source and target segments in your project. To do this, you can select File > Project QA, then select the type of QA report you want to run. Using these reports, the content developer can find errors the translator may have missed, such as formatting or punctuation inaccuracies, misuse of the termbase, or repeated segments.
  • Status The File List window pane lists each content file and various information for each. One of the columns in this window pane is named "Status." This column displays the translation status of each file (e.g., Untranslated, In Progress, Completed, Reviewed, Approved). The translation status can be set manually, or when certain actions are performed, the status is set automatically. After a translator returns a bundle and you merge it back into a Lingo project, the status of each file is updated, depending on the situation. If the translator only partially translates a file, the status changes to "In Progress." If the translator finishes translating all segments in a file, the status changes to "Completed." If the translator returns the file untouched, the status remains "Untranslated."
  • Review You can export translated content to a MadCap Contributor review archive file (LIREV) and send it to a third party for review. See Sending Translated Content for Review.

After ensuring that everything is completely translated, you can export the project to new output. See Exporting Translated Projects.