Unified localization

The latest approach in IXIA CCMS Web 7.3, known as unified localization, significantly departs from the approach to localization in previous releases of CCMS Desktop.

The unified model offers more flexibility and overcomes several limitations of the prior model:

Incompatibilities that surface between localization models and all its variations
Creation of unnecessary objects within the Content Store, slowing performance
The need for a high-level view of localization progress
Creation of separate kits for a map's dependent image objects

Incompatibilities between localization models and variations

The legacy model offered multiple variations, yet not all of the variations were available in all environments, so users had to choose an environment that might not prove flexible enough to fit a given situation or method.


Localization model	Sequential	Concurrent
Standard environment	Available	Available
DRM environment	Available	Not available
Pre-localization	Not available	Available
Non-incremental method	Available	Available
Incremental method	Available	Not available

The new approach unifies the identified variations into a single model that is available for all customers, regardless of environment.

Creation of unnecessary objects

The legacy model created a new object in the Localization collection that mirrored each object in the source for each destination language. For example, if you localized a map that referenced 100 topics for a total of 10 destination languages, the process created more than 1000 new objects. The only exception was if you used auto-translate.

The unified model removes this duplication from the localization process, so significantly streamlines and speeds the creation of a localization kit.

Need for a high-level view of localization progress

With the legacy approach, there is no good way to see the progress of a localization job or confirm the status of a topic in the translation workflow or compare the progress of multiple languages for a given map. With the new Translation Manifest, the unified model offers a mechanism for switching among specified destination languages for a map.

Creation of separate localization kit for images

CCMS Desktop localization kits require users to create a separate kit for any images that required translation, then import translated images back into the CCMS before importing the rest of the translated content. This two-step process is time-consuming and error prone. The unified model supports creation of a single kit with all the content you need to translate.

Considerations for the unified localization method

There are several important things to remember as you consider the unified method of localization. The relationship between your role, the objects you want to translate, and the status of those objects all play a part in the unified localization method, but the methodology used to manage the process is very different.

For users of legacy CCMS Desktop:

The approach in CCMS Web is a significant departure from its predecessor, so while it recognizes files localized in CCMS Desktop, you cannot edit them, and if you transition your legacy files to CCMS Web, you cannot undo this process. It is a one way street.

With content you localized in CCMS Desktop but want to interact with in CCMS Web, you can view the content and include it in CCMS Web-generated outputs, but you can't edit it.
With content you localized in CCMS Web, but want to interact with in CCMS Desktop, you can only view it in CCMS Web, not in CCMS Desktop.
The legacy Localization cycle only contains content localized in CCMS Desktop.
If you are having issues with the transition, it might have to do with your new access right for localization. Contact IXIA CCMS Customer Support.

For users of CCMS Web:

The new Translation cycle only contains content localized in CCMS Web.
The Translation Manifest is now the central point of access for all translated content.
When you create a Translation Manifest and generate the localization kit, no content is created. Instead, content is only created when you import the translated content.