Documentation Center

Configuring elements for pre-translation

List XML elements that are to be compared for pre-translation in the translation configuration file.

About this task

The elements in the translation configuration file are compared in the order that they are specified. As a best practice, configure top-level elements first. For example, when a complete <section> element is identical, you want to pre-translate the entire element rather than all child elements separately.

Procedure

  1. Login to the SDL LiveContent Architect web client as a user with an Administrator user role.
  2. Select Settings --> XML Translation Settings
    The Admin.XMLTranslationConfiguration.xml file is displayed in the right pane.
  3. Locate the section that begins <ComparisonElements> in the Admin.XMLTranslationConfiguration.xml file displayed in the right pane.
  4. Add an <xPath> tag within the <ComparisonElements> tags, in the format:
    <xPath>//*[contains(@class,' element/element ')]</xPath>
    where element/element indicates parent/child element tags.
    For example, to indicate that <section> tags within<topic> tags are to be pre-translated, enter:
    <xPath>//*[contains(@class,' topic/section ')]</xPath>

Example

The example below is a hierarchy of elements that are to be pre-translated that all fall within the <topic> tags. The hierarchy starts with a top level tag, <section>, within the <topic> tags. Other tags within <topic> are listed in order of significance for pre-translation.
<ComparisonElements>
    <xPath>//*[contains(@class,' topic/section ')]</xPath>
    <xPath>//*[contains(@class,' topic/example ')]</xPath>
    <xPath>//*[contains(@class,' topic/shortdesc ')]</xPath>
    <xPath>//*[contains(@class,' topic/table ')]</xPath>
    <xPath>//*[contains(@class,' topic/row ')]</xPath>
    <xPath>//*[contains(@class,' topic/ol ')]</xPath>
    <xPath>//*[contains(@class,' topic/ul ')]</xPath>
    <xPath>//*[contains(@class,' topic/li ')]</xPath>
    <xPath>//*[contains(@class,' topic/sli ')]</xPath>
    <xPath>//*[contains(@class,' topic/title ')]</xPath>
    <xPath>//*[contains(@class,' topic/navtitle ')]</xPath>
    <xPath>//*[contains(@class,' topic/alt ')]</xPath>
    <xPath>//*[contains(@class,' topic/indexterm ')]</xPath>
    <xPath>//*[contains(@class,' topic/term ')]</xPath>
    <xPath>//*[contains(@class,' topic/tm ')]</xPath>
    <xPath>//*[contains(@class,' topic/fn ')]</xPath>
    <xPath>//*[contains(@class,' topic/xref ')]</xPath>
  </ComparisonElements>
</InfoShareTranslations>
<topic> <title>Translation</title>
   <body><section><title>Configuring</title>
      <p>The translation of topics...</p>
   </section></body>
</topic>

In the above example, topic/section or body/section are both valid.