The purpose of exporting documents for localization is to extract the text added while customizing your content in a format that makes it convenient for translation.
Before exporting any documents for localization, you must create a duplicate of the complete set of related documents, including the glossaries, to be translated. The duplicated documents serve as placeholders for the translated content; therefore, one set of duplicates must be created for each target language. It is recommended that you create the duplicate for each target language in a separate, clearly identified Library folder.
After creating the duplicate, you can export it for localization from either the Library or the Outline Editor. If you create the duplicate in a separate folder as recommended, you can simply select the folder itself from the Library. Alternatively, you can select one or more individual documents.
Tip: You can select multiple documents using the standard Windows selection keys (CTRL+click and SHIFT+click).
After selecting content and initiating the export process, your next step is to set the export options.
Save Location and File Format
The first option is the location in which to save the localization file. The default location is the My Localization subfolder of the My Documents folder on your local hard drive, but you can choose any other location on your computer or server for which you have Write permissions. You must also specify a name for the localization file. This file name does not in any way affect the processing or translation of the documents it contains, but it is recommended that you use a meaningful name that reflects the intended translation process. For example, you might use the name Document Basics_EN_HU for content to be translated from English into Hungarian. Also note that certain reserved characters are not permitted in localization file names.
In addition to specifying the file name, you also must select the translation file format as either Microsoft Word or XLIFF. In both cases, the same text components of the selected documents are exported; the difference is in the intended translation process. Exporting to Microsoft Word format (file extension DOCX) provides an easily readable listing of text that is amenable to manual translation. Exporting to XLIFF format (file extension xlf) provides an XML-based file for use with translation tools that support this format. See Localization Using Microsoft Word and Localization Using XLIFF for more detail.
Content Selection
The second option allows you to export your selection only or your selection and all related documents. In general, documents linked as children of the documents in your selection are included as related, whereas those linked as parents are not. Any glossary assigned to one or more documents in the selection is also included as a related document. Click the View related documents link to display a list of all documents related to your selection.
Note: The content of a package document is not exported for localization.
Language
The third option is to specify the source and target languages. The source language is determined by the Developer and reflects the Language property of the selected document(s). The target language is the language into which the content is being translated. Note that only one target language can be selected. If the same content is intended for translation into multiple languages, this content must be duplicated multiple times, and each set of duplicated content must be exported separately with the appropriate target language specified.
During the Localization export process, the Developer extracts the custom Developer text included in the selected document(s) and writes it to a single localization file of the selected format (Microsoft Word or XLIFF). Included with the text is some required processing information, such as document and translation unit IDs, that is essential for the text to be imported successfully after translation and must not be changed. (See Localization Using Microsoft Word and Localization Using XLIFF.) The custom Developer text that is exported for localization depends on the document type as follows:
Module
- Document name - Roles
- Keywords - Description
Section
- Document name - Roles
- Keywords - Description
Topic
- Document name - Roles
- Keywords
- Custom bubble text, including formatting and markup for play modes and Player and document outputs (one or more translation units per topic frame, depending on play mode and output markup)
- String input text
- Implicit text (for string input action)
- Object names
- Jump-in points - Decision frame header and Decision path names
- Frame link tooltips - Frame comments (Expected Results, Author Notes, Instructor Notes) - Topic properties (Properties toolpane fields for Instructor Manual, Job Aid, System Process Document, and Test Document).
Package
- Document name
Web Page
- Document name
- Body text, including formatting. Note that the body text is segmented.
- Images(advisory title and alternative text)
- Tables (cell contents, caption, and summary) - Links (tooltip)
Assessment
- Document name - Roles
Question
- Document name - Roles
- Remediation text
- Question text
- Blank Answer text
- Option text
Glossary
- Document name
- Glossary terms
- Tooltips for glossary terms
A summary message appears if some of the documents you selected could not be processed. Clicking the View activity log link in the message displays a list of the results for each document.
The export creates either an XLIFF or DOCX file depending on your format selection. Selecting Cancel during the export for localization process displays a message with a link to a list of the documents that have already been exported. Although the partial localization file can be edited and imported, it includes only a subset of the documents intended for translation. Therefore, it is recommended that you delete the partial localization file and restart the process from the beginning.
Note: In this version of the Developer, the Web Page Editor creates web pages with a different underlying structure than those web pages created with previous versions of the Web Page Editor (legacy web pages). However, during the export for localization, the Developer converts old web pages to the new structure. This structure change affects the existing translation memory (TM) for localized content created with previous versions of the Developer.
Multi-user Considerations
In a multi-user environment, when you are online, you also have the option to choose local or server content. Local content includes the locally edited copies of all selected documents that you have checked out and the server versions of those not checked out to you. Use this option for documents in progress for review. Server content includes only the checked in versions of the selected documents. Any local changes to checked out documents are ignored. Use this option for final versions of documents.
You can also export while offline, but to do so, you must have the documents in your local cache.
Nevertheless, it is recommended that you check in all documents to be exported for localization and export the server content to ensure that you include the most up-to-date versions.
To export content for localization:
From the Library or Outline Editor, select the folder(s) and document(s) you want to export for localization.
You can select multiple documents using the standard Windows selection keys (CTRL+click and SHIFT+click).
On the Tools menu, point to Export and choose Localization.
Set the export options.
Click OK.
The Developer processes the selected documents, creating a single file containing all extractable text, and associated processing information, in the specified location.
If any errors occur, they are written to an activity log, and a Partial Export message box appears. You can click the View activity log link to view the results of the export or click OK to close the message box.