Exporting Translated Projects

When all of the content in a project or file is translated, you can export the work to the application, file, or location. For example, if a Flare project was translated, you can export your work out to a new Flare project; if a Word document was translated, you can export your work out to a new Word document. This translated project or file can then be opened, and output can be created from it.

Note If you have translated files for a Flare project, you also have the option of placing your Lingo project where the Flare author can access it. The author can then link directly to the Lingo project. This way, you do not need to export the Lingo project back out to a new Flare project. However, in order to use this process, the author must also have Lingo 11 installed on his or her computer in order to correctly build the multilingual output.

[Menu Proxy — Headings — Online — Depth3 ]

How to Export a Translated Project

  1. Select File > Export.

  2. (Optional) If you are working with a multilingual project, from the Language drop-down, select the language to include in the exported project, or select All Languages.

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

    Note You will not see this option if you are translating files in a multilingual bundle and need to export the files to return them to the content developer. This is because you must return all the files in the bundle, regardless of their language.

  3. (Optional) If you are translating non-project files and want to apply a code (e.g., "es" for Spanish) to the individual files you are exporting, select Append language code to files. This setting is beneficial if you want to flatten the exported files so you can see them side by side, instead of having all instances of the same file name without any language code attached to those files.

    Note If this option is not selected, the language code is used for the parent folder name for each of the exported languages (e.g., if you are translating to Spanish, the folder is named “es”). This option is not displayed if you are translating project files.

  4. (Optional) In the Destination Filename field, you can keep the name or enter a different one for the exported project.

  5. (Optional) In the Destination Folder field, you can click Browse to find and select a different location. Typically, you want to export the project to a location where the author can retrieve it, unless you plan to deliver the file(s) to the author in some other way (e.g., email).

  6. (Optional) If you want to create an additional ZIP file when exporting the project, select Make a zip file after export. If you do not select the check box, the project files are still exported, but a ZIP file is not created. If you do select the check box, the project files are exported and an extra ZIP file is produced.

    Note When you create a ZIP file on export, the folder structure is maintained.

  7. Click Export.
  8. (Optional) If you have not translated all of the files in the project, a confirmation dialog asks if you want to export the project with untranslated files. Click Continue to export the project, or click Cancel.
  9. (Optional) If the project has already been exported to the selected destination, a dialog informs you that the destination already exists. Lingo will permanently overwrite any updated files. Click OK to export updated and new files, or click Cancel.
  10. When the export completes, a dialog opens. You can click Yes to view the new project, or you can click No.

  11. (Optional) In the Exporting dialog, click one or both of the following:

    • Open Exported Project Opens the exported project in the appropriate program.

    • Save Log Saves the export log to the project folder.

      Note You can view saved export logs from the Project Properties dialog.

  12. Click Close.

What’s Next?

After exporting a project, you can inform the author, who can then open the translated project or file and create output for it.