Configure the incremental localization process for CCMS Web
The CCMS Web incremental localization process allows you to
start the localization process before all objects have an Authoring:done
or
equivalent status.
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.
To incorporate the incremental localization process in the workflow, make the following changes to the configuration files:
- Add a new status called
Localization:do not translate
that defines the available statuses for each object. The Localization:do not translate status identifies the objects that are not authorized for translation. - In the access rights configuration file, the
Localize
action defines the required statuses for objects at the time they go to the Localization cycle. - In the access rights configuration file, the
localize_api
action defines which statuses for each object are set to Localization:tb translated at the time they go to the Localization cycle. All statuses not defined in thelocalize_api
action are automatically set to Localization:do not translate when they go to the Localization cycle. - In the access rights configuration file, the
Prepare kit
action defines which objects and at which status get included in the localization kit.
Objects set to Localization:do not translate are excluded from localization kits that are prepared by IXIA CCMS.