Enable the linguistic review process

The linguistic review process removes the translate="no" attribute from all content (including auto-translated text) when preparing the localization kit.

Note: For this procedure to work, the auto-translation feature must be enabled.
The linguistic review process works as follows:
  1. The user runs the Prepare Localization Kit command on localized content that is in Localization:review.
  2. The IXIA CCMS looks up the linguisticreview.xml file, which lists the elements that should keep the translate="no" attribute (for example, <codeblock> elements).
  3. IXIA CCMS prepares the localization kit and removes the translate="no" attribute from all elements, except for those in the linguisticreview.xml file.
Important: Make configuration changes in a test environment and confirm they work before copying them to a production environment. For dedicated SaaS deployments, test the changes and then ask IXIA CCMS Customer Support to copy the changes to your production environment.
  1. In the TEXTML Administration perspective, connect to your server.
  2. Locate the accessrights.xml file in the repository's /system/conf collection.
  3. Check out the file and open it for editing.
  4. Configure the access rights to the Prepare Localization Kit command:
    1. Look for the line that starts as follows:
      <method name="Prepare kit" 
    2. If the <status>Localization:review</status> status is not configured for maps, add it.

      For example:

      <current>
         <type name="map">
            <statuses>
               <status>Localization:tb translated</status>
               <status>Localization:in translation</status>
               <status>Localization:review</status>
            </statuses>
         </type>
         <type name="topic">
            <statuses>
               <status>Localization:tb translated</status>
               <status>Localization:in translation</status>
            </statuses>
         </type>
      </current>
    3. Look for the line that starts as follows:
      <method name="prepareLocalizationPackage_api" 
    4. If the <status>Localization:review</status> status is not configured for maps, add it.

      For example:

      <current>
         <type name="*">
            <statuses>
               <status>Localization:tb translated</status>
               <status>Localization:in translation</status>
               <status>Localization:review</status>
      
            </statuses>
         </type>
      </current>
  5. Add the linguistic review process to the accessrights.xml file:
    1. Locate the following line:
      <!-- ********************** API METHODS DO NOT MODIFY ********************** -->
    2. Just before this line, add the following <method> code to set access rights for the linguistic review process:
         <!-- Linguistic Review -->
         <method name="LinguisticReview" type="api">
            <notify enabled="false"/>
            <conditionset operator="any">
               <condition>
                  <current>
                     <type name="topic">
                        <statuses>
                           <status>Localization:review</status>
                        </statuses>
                     </type>
                     <type name="map">
                        <statuses>
                           <status>Localization:review</status>
                        </statuses>
                     </type>
                  </current>
                  <users>
                     <groups>
                        <group name="Everyone"/>
                     </groups>
                  </users>
               </condition>
            </conditionset>
         </method>
  6. Save, close, and check in the file.
  7. Locate the linguisticReview.xml file in the repository's /system/conf collection.
  8. Check out the file and open it for editing.
  9. By default, linguisticReview is set to enabled="false". Change the attribute value from "false" to "true".
  10. Add new <class> elements to specify the classes of any elements that you do not want translated.

    To find an element's class, select the element in your XML editor and view its attributes. For example, to add <codeblock> to the list of elements not to translate, add the following line:

    <class name="+topic/pre pr-d/codeblock "/>

    Be sure to preserve the initial - or + as well as the trailing space before the closing quotes.

  11. Save, close, and check in the file.
  12. Inform users of the changes.
    The changes will be applied automatically once users close and then reopen their CCMS Desktop. Users can also apply the changes without restarting their CCMS Desktop by clicking IXIA CCMS > Synchronize Configuration. Additionally, refresh IXIA CCMS Web so that users will see the change reflected there.