Configuring the localization model used

Sequential localization model

In this model, when you localize a source object for the first time, the CCMS creates a new object in the target language. This language object is then updated when a new version of the source object is sent to localization, so there is a one-to-one mapping between the files in localization and their authoring sources. In the sequential localization model, the files are sent to the translation team in DITA format.

Concurrent localization model

In this model, each localization creates a "branch" of the content in localization, one set for each language selected. Therefore, a new file is created in the localization workflow each time a new revision of a source object is localized. There are two flavors of the concurrent localization model:

• Node-based localization method: In the node-based localization method, when the files are exported to the localization kit, they are converted into an XLIFF format used by translation memory tools. They remain in DITA format in the Content Store.
• Concurrent localization method: The concurrent localization method includes the following new features:
  • Ability to generate the localization kit in XLIFF and DITA formats
  • Very flexible auto-translation process, which can be configured to ignore changes that you consider minor such as extra spaces, punctuation, <draft-comment> elements, etc.
  • A new status in the workflow that indicates whether a document was completely auto-translated by the system
  • A new report that provides detailed feedback on the localization process
  • An improved localization kit that provides more content, such as a document that includes all the source text and images to provide context for the translation

You configure the localization method used for your deployment in the localizationManagers.xml file by specifying a localization manager.