Translation management
Content Manager helps translation coordinators by minimizing the content that needs to be translated, determining the target languages following the reuse relationships, and by applying In-Context Perfect Matching.
Content Manager helps translation coordinators by tracking topics that are reused in many different publications each with different translation requirements.
Introduction
In traditional systems, entire projects are sent to translators because such systems don't and can't track the components that change. This has many disadvantages, one being that translation needs to wait until the entire project is finished. Furthermore, XML files that were not changed are translated again because users don't know which XML files were updated.
Minimize the content that needs to be translated
Content Manager only sends objects that were changed, into the translation workflow. When a new version of a topic is approved in its source language, Content Manager generates a file for all target languages. This is only done after an object has gone through all review cycles because then the content is stable enough to be translated.
Determine the target languages
Content Manager inherits the target languages from the DITA map level. Since a topic can be reused in many different publications each with different translation requirements, this makes it possible to track which topic needs to be translated into which language.
In-Context Perfect Matching
Content Manager also pre-translates content when generating target language files by comparing the released XML file with its previous release in the source language. XML elements that have not changed between the two versions are pre-translated. This means that the previous translation is copied into the generated target language file.
- A first version of a topic is available in English and in French.
- A second version of the English topic is released.
- Content Manager compares the second version in English with the first version in English and detects that one XML content element is updated.
- Content Manager prepares the French version for translation by copying the French content for the elements that did not change from the first version in French to a second version so that only the block that was modified remains to be translated.
- The French content is added next to its English counterpart. Pre-translated elements are marked with a special XML element (<preTranslation>).
In-Context Perfect Matching and Translation Memory tools
<body id="5E33769DFF71">
<preTranslation>
<title lang="en">Front seats</title>
<title lang="de">Vordersitze</title>
</preTranslation>
<preTranslation id="7CB9030FDBBD">
<section id="7CB9030FDBBD" lang="en">
<title>Manual seats adjustment</title>
<ptxt>Pull the lever up while you slide the seat forward or backward to the desired position.</ptxt>
</x:section>
<section id="7CB9030FDBBD" lang="de">
<title>Manuelle Sitzeinstellung</title>
<ptxt>Ziehen Sie den Hebel nach oben, während Sie den Sitz in die gewünschte Stellung nach vorn oder nach hinten schieben.</ptxt>
<section>
<preTranslation>
<body>
When the translated file is uploaded to the repository again, the remaining text in the source language as well as the <preTranslation> elements are removed.
Translating the content
The new language objects are sent to the inbox of the translation coordinators, or directly to translators. They can push it to the next status in the workflow or check it out. The translation is made with the proper translation tools outside Content Manager or XML editor. When the translation is ready, it is checked in and sent to the next status in the workflow.
Alternatively, the coordinator can create a translation package by selecting translation objects and by exporting them to a zip file. The coordinator gives the translator access to the zip file. As soon as the translator is ready with the translation, the coordinator imports the translations in bulk. This scenario is used when the translator does not have access to the system (e.g. when working with external translation agencies).
Benefits
Most translation-memory systems are not context-sensitive. For example, in the English sentence "Remove the battery", the word "battery" can be translated in two ways in Spanish, depending on the kind of battery that is used ("a car battery" versus "a torch battery"). That is why translators must review all translations produced by a translation memory, even when translations are marked as a perfect match (the so-called 100% matches). Reviewing means checking if the sentence is used correctly in a particular context.
Often, different translators translate a sentence in slightly different ways. As a result, one sentence in a given source language may correspond to two or more translations. In that case the translator has to make a manual selection that takes time.
By using the Content Manager In-Context Perfect Matching functionality, these translation review costs can be avoided.
Notes
- The pre-translation process copies elements from previous versions of language objects with the same logical ID, therefore pre-translation is not done on the first version of a topic or map.
- When comparing two versions, the XML structure of the documents is compared. Any structural change is interpreted as a modification and consequently there is no pre-translation. For instance, an extra white space between two tags, or an invisible tag added by an XML editor is considered a structural change so no pre-translation is done.
- The comparison granularity is DTD-specific and is configured by the system administrator.
- The translation of reusable elements is done automatically. The available translation for the appropriate version of the reusable element is used.
Automatic Generation of Target Languages
When a new version of a topic is approved in its source language, Content Manager generates a file for each target language. Only target languages that are explicitly requested (requested languages property) or inherited from the DITA map level are generated. For example, if an object for which French and German are explicitly requested, is used in a Spanish publication, a Spanish target is also generated.
This translation workflow is triggered automatically when a topic, an image, a library topic, or map is released.
- Set the requested language(s) property on any object that needs to be translated.
- Release the object. The required target languages are generated in the background.