XLIFF 1.2 support

Introduction

In censhare, segmentation of the Adobe ICML format or another XML dialect may be controlled. Segments are the basis of the translation process: This proceeds segment by segment. A segment normally corresponds to a sentence in the text to be translated.

The segmentation rules specify how the segments are composed. censhare uses the Standard Segmentation Rules eXchange format for this.

When the translated text comes back, censhare stores it in the appropriate variant of the original text. Translation Memory Systems (TMS) use segments as the basis for checking whether something has already been translated. Depending on the degree of similarity, the translation may be inserted automatically or manual checking may be required.

Configuration of the segmentation for export

Before a user can start the export of a text item to XLIFF, a tag mapping must be defined with the admin client for the appropriate XML dialect. An example of this is Adobe's ICML. With ICML, censhare knows how to handle the element names which appear there, such as “Content” or “ParagraphStyle-Range”. This may be converted into one or a pair of XLIFF inline tags. In this way, the text markup present in ICML remains available in XLIFF and provides the translator with additional information.

For each element name, it can be specified whether its appearance marks the start of a new segment. For example, this might make sense with the element name "br" (Break), which causes a line break in Adobe ICML. Here, it is important that the segments represent sensible translation units such as a sentence. Division of a sentence into multiple segments on the basis of character styles is not generally helpful for translation. Translation memory systems may then be unable to find any matching translation segments in their database.

Export/import for XLIFF is defined in a censhare module, alongside mapping. censhare uses the "strict" variant for version 1.2 of XLIFF, which only allows attributes and elements which are also defined in XLIFF 1.2.

Customer Benefits

• Different translation workflows: Sequential or parallel generation of the translation

• Linking of translations and localizations with the original text by means of variants

• Notification or automatic update on later alterations to the original layout, text or other content

• Application of the translation solution already used in the company or the service provider

• Export of text in XLIFF for further processing with a translation solution

• Import of the XLIFF data after completion of translation

• Use of the Segmentation-Rules-eXchange (SRX) standard to define the segmentation rules for translation elements

Application Case

• Creation and coordination of international sales literature

• Creation of marketing literature in different languages with the design adapted for the regional variation

• Production of multilingual magazines

• Production of literature for different languages in a multi-stage process, such as from German via English to Tagalog (the Philippines)

Background information: Using external systems for translation

Many companies are active on foreign or even international markets. Technical magazines have foreign language editions or are directly produced in multilingual form. With censhare, companies create this multilingual content - whether for print, online, mobile or E-books - in one single system. They control and monitor production not only for the original language, but also for all the translated versions.

In order to translate the text for particular languages, companies often use service providers. These may then involve additional freelance translators. In many cases, special translation solutions are used for this. censhare is compatible with these systems.

Then the translation process begins for technical terms, the actual text and their correction. At the end, the translation system re-exports the completed text in XLIFF. After import into censhare, it is available for further production.