Configure the incremental localization process
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.
Typically, the map and all its children should have an
Authoring:done
or equivalent status before you can begin with localization.
When you implement the incremental localization process, you define each acceptable status
before the objects go into the Localization cycle. For example, instead of having the map, the
topics, and all the images at Authoring:done
before starting the localization
process, you can configure it so you can begin the localization process even if some of the
topics still have an Authoring:work
status.
- Add a new status called
Localization:do not translate
to the configuration files which defines the available statuses for each object. The Localization:do not translate status identifies the objects that are not authorized to be translated. - In the
Localize
action in the access rights configuration file, define the required statuses for objects at the time they get sent to the Localization cycle. - In the
localize_api
action in the access rights configuration file, define which statuses for each object are set to Localization:tb translated when they are sent to the Localization cycle. All statuses not defined in thelocalize_api
action are automatically set to Localization:do not translate when they are sent to the Localization cycle. - In the
Prepare kit
action in the access rights configuration file, you define which objects and in which status are included in the localization kit.
Objects set to Localization:do not translate are excluded from localization kits that are prepared by IXIA CCMS.