• Export Content for Localization
  • Export Content for Localization
  • "036ca9d4-ee8e-4d15-a3a7-0ed6bc3f98da
  • 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
  • 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:
  • After selecting content and initiating the export process, your next step is to set the export options.
  • 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
  • Save Location and File Format
  • reserved characters
  • Localization Using Microsoft Word
  • Localization Using XLIFF
  • The second option allows you to export your selection only or your selection and all
  • Content Selection
  • related documents
  • Note:
  • The third option is to specify the source and target languages. The source language is determined by the Developer and reflects the
  • Language
  • Language property
  • 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
  • Localization Using XLIFF
  • Module
  • - Roles
  • - Description
  • Section
  • - Roles
  • - Description
  • Topic
  • - Roles
  • - Decision frame header and Decision path names
  • - 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
  • Web Page
  • (advisory title and alternative text)
  • caption, and summary)
  • - Links (tooltip)
  • Assessment
  • - Roles
  • Question
  • - Roles
  • Glossary
  • 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.
  • 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.
  • The export creates either an XLIFF or DOCX file depending on your format selection.
  • 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.
  • Note:
  • 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.
  • To export content for localization:
  • From the Library or Outline Editor, select the folder(s) and document(s) you want to export for localization.
  • On the
  • Tools
  • Export
  • Localization
  • Set the export options.
  • Click
  • OK