Concurrent localization model
In the concurrent localization model, each time you send a new revision of a source object to be localized, a new "branch" of the content is created for each target language. So you can have multiple revisions of the source object being translated at one time.
The concurrent localization model is more flexible than the sequential model, but it can lead to a much larger repository size and increase the risk of duplicate translations.
First localization of an object
The figure shows the process for the first translation of an object in the concurrent localization model.
| Stage | Description |
|---|---|
| Localize |
When a source object is translated into a language for the first time, the system creates a new object in the target language (referred to as a language object). A language object has its own Revision number as well as an Authoring Revision property, which stores the revision number of the source object when it was sent for translation. For example, you send a source object that is at Revision 6 for translation. A new language object is created in Localization with its own Revision number of 1 and an Authoring Revision of 6. The language object keeps the same name as the source object, but the name includes the authoring version number. For example, you localize a document named abc1386692219292.xml that is at revision 6. A file named abc1386692219292_00006.xml is created in each target language. Its content is still in the original language, but its language attribute is set to the target language. The language object has the tb translated state. |
| Create localization kit |
When you create the localization kit, the language object still has the same Revision number, but its state is now in translation. The files in the localization kit are extracted from the Content Store either in their original DITA source, or converted to the XLIFF format if your are configured to use XLIFF. |
| Import localization package |
When translated content is imported into the Content Store, a new revision of the language object is created (for example, Revision 2). The Authoring Revision is never updated so that it is always possible to correlate a language object with its original source. Its state changes to review so that the translated content can be reviewed internally. |
| Localization review |
If the translation is updated during the review process, a new revision of the language object is created. When the translation is approved, its state is changed to Done, and you can now publish the localized map. |
Subsequent localizations
The figure shows the process for subsequent translations of an object in the concurrent localization model.
When you send a new revision of a source object for localization, IXIA CCMS Desktop does not update the existing language object. It checks to see if this revision has already been sent for localization (for example, if it was part of a another map already sent for localization). If this revision is already in translation, the localization process skips the file.
If this revision has not been sent for localization, it creates a new object in the target language, and its name includes the authoring version number (for example, abc1386692219292_00009.xml). This new localization object has no impact on the previous translation (named abc1386692219292_00006.xml). This is why this model is concurrent: multiple language objects of the same source object exist concurrently.
The new language object has its own revision number starting at 1, and its status is set to Localization:tb translated.
Auto-translation is always enabled for the concurrent localization model. If a previous translation exists with content in the Localization:done status, CCMS Desktop auto-translates the content using the translated text from the previous version.
If the language object was fully translated during auto-translation, CCMS Desktop creates a new revision of the language object with the auto-translated content and sets its status to Localization:machine translated (or its equivalent in your workflow, depending on your configuration). Otherwise, the next step depends on whether your system is configured to accept partially auto-translated documents.
If partially-translated documents are accepted, then the CCMS Desktop creates a new revision of the language object with the partly translated content and sets its status to Localization:tb translated. Otherwise, the partial translation is rejected and the source content is sent in the localization kit.
With the concurrent localization model, there is no dependency between the various authoring revisions that are sent to translation; a new authoring revision can be sent to translation independently of the localization status of the previous authoring revision.