Prepare the localization kit

Once the files are in the Localization cycle, a localization kit is prepared for each language and sent to the translation team.

Requirements:

  • If preparing a localization kit for a map, the map's title must be in an element – not an attribute.
  • The map or topic must have the status Localization:tb translated (or its equivalent in your workflow).
The following table describes the contents of the localization kit according to the localization method configured:
Table 1. Localization kit contents
Sequential localization method Concurrent localization method
A ZIP file that contains the following:
  • A <language> directory (for example, ja-jp) that contains the map and its topics in DITA format. If auto-translation is enabled and a previous translated copy existed, the files will contain the automatically translated text. Depending on the configuration, this directory may include the .image containers for the images in the map for context.
  • (Optional) A file called originals.zip. This file is saved in the <language> directory and contains the current version of the document sent for localization in a format configured by your CMS administrator (for example, PDF, HTML, etc.). If auto-translation is enabled, this document includes the auto-translated text.
  • (Optional) A file called lasttranslation.zip. This file is saved in the <language> directory and contains the previous translation of the document in a format configured by your CMS administrator (for example, PDF, HTML, etc.).
A ZIP file with the content in XLIFF format, as follows:
  • The map and its topics in XLIFF format. Each XLIFF translation unit contains the original source text. It will also contain the automatically translated text (or a copy of the source text if auto-translation was not possible). Depending on the configuration, this directory may include the .image containers for the images in the map for context.
  • Two PDF files: filename_current.pdf and filename_lasttranslation.pdf (optional). These contain the current version of the document (including auto-translated text, if available) and the previous translation (if there is one).
A ZIP file with the content in DITA format, as follows:
  • A <language> directory (for example, ja-jp) that contains the map and its topics in DITA format. If auto-translation is enabled and a previous translated copy existed, the files will contain the automatically translated text. Depending on the configuration, this directory may include the .image containers for the images in the map for context.
  • (Optional) A file called originals.zip, which contains the current version of the document sent for localization in a format configured by your CMS administrator (for example, PDF, HTML, etc.). If auto-translation is enabled, this document includes the auto-translated text.
  • (Optional) A file called lasttranslation.zip, which contains the previous translation of the document in a format configured by your CMS administrator (for example, PDF, HTML, etc.).
Note: A localization kit must be prepared for each of the target languages.

The localization process requires a substantial amount of system resources. If you are localizing several maps in many different languages you may notice an impact on your computer's performance.

To prepare the localization kit:

  1. In the Cycles panel of the Search view, select the Localization checkbox.
  2. In the Document Types panel of the Search view, select Maps or Topics, depending on whether you are localizing a map or a topic.
  3. In the Languages panel of the Search view, select the target translation languages.
  4. Click the Search button.
    All maps or topics that are being localized in these languages appear in the Search Results view.
  5. In the Search Results view, right-click the required map(s) or topic(s) and select Localization > Prepare Localization Kit from the menu.
    The Generate Kit dialog appears as the localization kit is generated and zipped.
  6. After the localization kit is prepared you have the following options:
    • If Auto save is enabled, the Generate Kit dialog displays the location where the file was saved. Click OK.
    • If Auto save is not enabled, the Save As dialog appears. Confirm or change the proposed filename and location, then click Save.
The localized objects now have the status Localization:in translation (or its equivalent in your workflow).
When the files returns from translation, it must be imported back into the system.