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.

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:

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 Multi-user Considerations

ProcedureTo export content for localization:

  1. 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).
     
  2. On the Tools menu, point to Export and choose Localization.
     
  3. Set the export options.
     
  4. 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.

Table of Contents  Back

Export_Content_for_Localization