Localization process

This section provides information and instructions about how to manage localization in IXIASOFT CCMS.

The following diagram shows an overview of the localization process.

Figure: Localization process
Localization process
Note: The process is based on the default localization workflow provided with IXIASOFT CCMS. Your workflow and its statuses may differ.

Stages of the localization process

The following table summarize the key points at each stage of the translation process.

Stage Description

The process begins when you select the Localize command and specify the set of target languages. When you localize a map, copies of the map and its contents (topics, images, and referred topics) are created in the localization area and given the status Localization:tb translated. There is one set for each language you select. When you localize a topic, that topic, its images, and referred topics are created.


If auto-translation is enabled, the CMS tries to auto-translate as much of the content as possible based on previous translations of the same content.

This occurs after you select the Localize command and target languages.

Create localization kit

The next step is to prepare the localization kit. This is the set of files that you send to the translation team for localization.

There are different kinds of localization kits:
  • The localization kit contains the maps and topics to translate. The files are provided in XLIFF or DITA format. Either format is available unless you use the node-based localization model, where only XLIFF is available. This kit may also contain the following files:
    • PDF files of the current version and the previous translation (if any) to provide context.
    • The .image containers for the images referenced by topics being translated. It doesn't include the actual images.
  • The image localization kit contains the images that are included in the map or topic that need to be translated. It includes all the image formats available so that they can all be localized. Images are sent in a separate localization package since they are treated differently in translation.

After you create the localization kits, the files are in the Localization:in translation status.

Import localization package

When the localized files are returned from translation, they are imported back into the Content Store.

You import the localized images back into the system first using the Import localized images command. Then you import the localized map and its topics using the Import localized content command.

The files change to Localization:review.

Localization review

You review the content of the localized files. You can return them to the Localization:tb translated status if there are issues, or you can complete the process by putting the files in the Localization:done status.

When the map and all its contents have reached the Localization:done status, you can create a snapshot of the map.