About incremental localization

The incremental localization process for IXIA CCMS Desktop allows you to start the localization process without having all the objects in the Authoring:done status or the equivalent status in your deployment.

Important: The incremental localization process is applicable only to the sequential localization model.

You can start the localization process on a map even if the map and its children are not in the Authoring:done status. This means that you can send topics to be translated as they become ready instead of having to wait until all objects are done. In fact, if you localize individual topics and images, IXIASOFT strongly recommends that you use the incremental localization process rather than sending them outside the context of the map.

When the incremental localization process is configured, a new status called Localization:do not translate is added to the workflow. It identifies the objects in the Localization cycle that are not authorized to be translated.

If objects in the Localization:do not translate status are included in the localization kit when it is prepared, the system automatically adds the translate="no" attribute to the root element of those objects so translation vendors can identify which files are not to be localized, and removes all the ixia_locid attributes from the elements contained in the objects to ensure that they cannot be imported after the localized files are received.

How the process works

  1. The map and each object in the map is set to a status which can be sent to the Localization cycle. Localize is enabled.
  2. You right-click the map and select Localization > Localize. The map and all its children are sent to the Localization cycle.
  3. In the Localization cycle, each object that is set to a status which is authorized to be translated changes to Localization:tb translated (or the equivalent status in your deployment), and each object set to a status which is not authorized to be translated changes to Localization:do not translate.
  4. The process of preparing a localization kit is unchanged, except if your administrator has configured the kit to include the objects set to Localization:do not translate. For objects set to Localization:do not translate, the translate="no" attribute is added to the root element of those objects, and the ixia_locid attributes are removed from the elements.
  5. When the kit returns from the translation vendor, all objects set to Localization:do not translate, if contained in the kit, will not be imported.
  6. As you repeat the process, some objects that were not in a status which is authorized to be translated in the previously prepared kit may have moved into a status which is authorized and, therefore, become set to Localization:tb translated.