Comparison of the two localization models

There are advantages and disadvantages to each IXIA CCMS Desktop localization model. This section describes the pros and cons of each model so that you can select the model that best fits your needs.

Sequential localization model for IXIA CCMS Desktop

The sequential localization model is the simpler of the two models. It creates a simpler content structure in the localization folder with less content duplication.

It has the following advantages:

  • The localization process is faster
  • There is a one-to-one relationship between the files in localization and their authoring sources
  • The files in localization have the same names as the files in authoring
  • The localization model does not need to remap links
  • The files in localization are more independent from each other, which makes it easier to do "localization in advance", that is, localizing some content before the entire document is complete in authoring
  • It creates a simpler content structure in the localization folder with less content duplication

As a disadvantage, the sequential localization model does not allow an object to be sent for translation if a previous revision is still being translated. It has to wait for the previous translation to be completed.

This means that new a revision can be sent for translation only if one of the following is true:

  • The previous revision has not yet been sent for translation (i.e., its status is at "localization:tb translated")
  • The previous revision has been translated and reviewed (i.e., its status is at "localization:done")

Concurrent localization model for IXIA CCMS Desktop

The concurrent localization model has the following advantages:
  • It is more flexible than the sequential model
  • Ability to generate the localization kit in XLIFF and DITA formats
  • Flexible auto-translation process can be configured to ignore changes that you consider minor, such as extra spaces, punctuation, and <draft-comment> elements.
  • New revisions of the source content can be sent for translation at any point in time
  • If two maps use the same topic but they are published with different revisions of the topic, both maps can be translated at the same time, since each will use a different file for the topic

However, the concurrent localization model has the following disadvantages:

  • It creates more objects in localization than there are in authoring, so the size of the database keeps growing even if the number of topics in the source content is stable. (The growth rate is multiplied by the number of target languages.)
  • New revisions sent for translation before a previous revision has completed its translation may lead to duplicate translations. (The new revision does not pick up the translation from the previous one.)
  • translation managers must carefully control when content is sent for translation to maximize reuse and lower cost.