Enable auto-translation in CCMS Web

Enabling auto-translation involves making changes to the system configuration and to the Output Generator configuration.

About this task

Procedure

  1. In the triggerswebplatform.xml system configuration file, enable the AddLocalizationIdTrigger trigger.
  2. Optional: Configure which elements have ixia_locid added.
  3. In the Output Generator configuration, copy the LocalizationKit preprocessor from %OutputGenDir%/conf/preprocessors.xml to %OutputGenDir%/conf/client/preprocessors.xml.

    Do not edit the LocalizationKit preprocessor in %OutputGenDir%/conf/preprocessors.xml. Any changes you make to the file in this location are likely to be overwritten during an upgrade. Always copy the preprocessor to the client preprocessors.xml file and make changes there.

    Note: If you are using OGAT, follow your usual process for updating files using that tool.
  4. In your copy of the LocalizationKitpreprocessor, change the value of the autotranslate parameter from false to true:
    <parameter name="autotranslate" value="true" />
  5. In the same preprocessor, set the value of the acceptPartialTranslate parameter as follows:
    • true: If the document is not fully translated, bring forward the translated text and leave the untranslated text in the source language. In other words, send mixed-content documents in the kit.
    • false: If the document is not fully translated, do not bring forward the translated text. If the document is fully translated, bring forward all the translated text. In other words, send only fully translated documents and fully source language documents in the kit.
    <parameter name="acceptPartialTranslate" value="true" />
  6. Save and check in the client preprocessors.xml file.
    Auto-translate is now enabled. You do not have to restart the Output Generator.

What to do next

All segments in the Authoring content must have an @ixia_locid attribute so the auto-translate process can compare them to the equivalent segments in previous translations. If the trigger that adds @ixia_locidwas recently enabled, you might have to check out and release the objects to trigger the addition of @ixia_locid.