Ektron CMS400.Net Reference

>>Working with Multi-Language Content > Using the Language Export Feature

Using the Language Export Feature

The Language Export feature lets you copy content into XLIFF files that can be submitted to a translation agency or translated "in house." When the translation is complete, you import translated content to Ektron CMS400.NET.

The Language Export feature lets you translate the following kinds of CMS information.

content, including summary, comments, and metadata

forms, including response message, comments, and metadata

all menus (you cannot choose individual menus)

file assets (Office documents, managed files, etc. You cannot export. zip files.)


What is XLIFF?

XLIFF (XML Localization Interchange File Format) is a format used to exchange localization data between participants in a translation project. This format lets translators concentrate on the text to be translated, without worrying about its layout. The XLIFF standard is supported by a large group of localization service providers and localization tools providers.

To learn more about XLIFF, visit these Web sites:



See Also:

Overview of Exporting/Importing Translation Files

Creating the .zip File

Importing Translated Files into Ektron CMS400.NET

Supported Versions of XLIFF

Ektron CMS400.NET supports versions 1.0, 1.1, and 1.2 of the XLIFF standard. You specify the version you are exporting in the web.config file, using the ek_XliffVersion element. Any listed version can be imported.

SDL Trados Studio 2009

Trados is a commonly used translation tool. SDL Trados Studio 2009 supports XLIFF 1.1 and 1.2, which are the recommended versions for use with Ektron CMS.

If you are using Trados (an earlier version of the product), it only supports XLIFF 1.0. Note that Ektron CMS400.NET 6.1.4 and older default to XLIFF 1.1. In this case, change the XLIFF version in the web.config file as described in Supported Versions of XLIFF.

Overview of Exporting/Importing Translation Files

1. You select content to translate. You can select:

a content item

a folder - all content in the folder is selected; all subfolders of the selected folder may be included

all menus

all taxonomies

2. Ektron CMS400.NET converts the selected content to XLIFF files. You can prepare the files for translation into several languages at once.

A separate .xlf file is created for each item. Then, all .xlf files for a language are compressed into one .zip file. A separate .zip file is created for each language.

3. Transmit the.zip files to a translation agency, which converts them into the new language(s).

4. The translation agency returns the files.

Alternatively, the files could be translated "in house."

5. Import the files into Ektron CMS400.NET. If the editions of the content do not exist in the target language, they are created.

Creating the .zip File

To create one or more .zip files for translation, follow these steps.

See Also: Using the Language Export Feature


Note: Only members of the Administrator User Group and those defined in the Manage Members for Role: XLIFF-Admin screen can create or import XLIFF files. See Also: Using the Roles Screens.

1. To translate one content item, navigate to its folder then click it.

To translate all content in a folder (and, if desired, all of its subfolders), navigate to its View Contents of Folder screen.

To translate a menu, go to Content Tab > Menus.

To translate a taxonomy, go to Content Tab > Taxonomy and check the taxonomies to translate.

2. Click Export for Translation (). (On the View Contents of Folder Screen, choose Action > Export for Translation.)

3. The Export for Translation screen appears.

Note: The Include Subfolders field only appears if you click Export for Translation from the View Contents of Folder screen.

4. To include content in all of a selected folder’s subfolders, check Include Subfolders.

5. The language of items being translated appears in the Source Language pull-down. If this is not the correct source language, select the correct one.

6. All enabled languages are selected under Target Language. (See Also: Determining Which Languages are Available).

7. To translate the content into all languages, proceed to the next step.

To translate the content into some languages, uncheck the languages that you do not want. You can uncheck the box in the header row (illustrated below) to uncheck all, then only check the ones you want.

8. Click Create XLIFF Files for Translation ().

9. Ektron CMS400.NET creates one .zip file for each language. The .zip file includes an XLIFF file for each selected content item.

Note: If content in a target language was edited more recently than the source language edition, that content is excluded from the .zip file.

The History section of the Export for Translation screen displays the translated files.

The history lists the .zip file created for each language. (.zip files are indicated by the WinZip icon ().) To the right of the icon are

the flag of the source language

an arrow indicating the direction of the translation

the flag and name of the destination language

the size of the zip file

Note: The top of the history window displays the most recently exported/imported files.

10. To review the items in a zip file, click + next to Extracted. When you do, each content item’s ID number, title, and last edit date appear.

11. Click the blue text of a .zip file. The File Download window appears.

Note: If you want to review the XLIFF files within the .zip file, click Open.

12. Click Save. The Save As window appears. Navigate to the folder where you want to place the zip file and click Save.

13. Transmit the files to the translation agency.

Note: When the translation agency returns XLIFF files, their extension must be .xlf or .xml. Other than that, the file name is not important.

File Naming Patterns




item identifier[item ID]_[new language hexadecimal code][two letter new language code].xlf

item identifier options:

- content: cont

- form: form

- menu: s

- menu item: s

- taxonomy: t

item ID varies, depending on whether the item is content, a form, a menu, or a menu item

- content: content ID number

- form: form ID number

- Menu: menu ID number

- Menu item: menu ID number


xlf[timestamp in format yyyymmddThhmmss]_u[user ID] _ [new language hexadecimal code]-[two letter language code].zip

The user ID indicates which user performed the export or import.

Importing Translated Files into Ektron CMS400.NET

To import translated files into Ektron CMS400.NET, follow these steps.

See Also: Using the Language Export Feature

Note: Only members of the Administrator User Group and those defined in the Manage Members for Role: XLIFF-Admin screen can create or import XLIFF files. See Also: Using the Roles Screens.

1. From the Ektron CMS400.NET Workarea, choose Settings > Import XLIFF Files.

2. Click Browse and navigate to the folder that contains the translated files.

3. Select the files to import.

4. Click Upload and Import ().

5. Ektron CMS400.NET creates new or updates existing foreign-language editions of the imported content/menu/taxonomy.

6. Information about the imported file appears in the history area of the Import XLIFF Files screen. You can click plus signs (+) to see increasing levels of information about the imported content.

When you import a file, the comment Translated appears next to it.

For each new edition:

If the content title is the same as the source edition, the next available number is appended to the title to distinguish it from the source. For example: Henry Williams(1).

its status matches the source content's status. Typically, its status is checked out. When imported, the content can enter the approval process just like other content.

its history indicates it was checked in at the time the report was run

for content, the following properties are inherited from the original content:

- Smart Form See Also: Working with Smart Forms

- content searchable

- approval method See Also: The Approval Method

date created and last edit date are captured from when the content is imported

the last user to edit is captured by user who imported the file

After you import the translation files, Ektron CMS400.NET removes them from the file system.

Note: If an error exists in any of the files, the erroneous files are moved into a subdirectory. The directory is created using a timestamp. For example: uploadedFiles\localization\merged\xlf20060208T141841_u1\error\.

Button image



Ready for translation

Automatically applied when content status changes to Approved. See Also: Content Statuses

Manually applied when authorized user clicks button and changes status to Ready for Translation.

Note: You may apply this status to unapproved content if it needs translation before the site goes live.

Not ready for translation

Automatically applied when content status changes to anything other than Approved. See Also: Content Statuses

Translation status changes if

authorized user clicks button and chooses ready for translation

content's status changes to approved

Should not be translated

Lets you prevent content from being translated.

Translation status changes only if authorized user clicks button and chooses ready for translation.

If you create an .xlf file for a folder, only content whose translation status is ready is included in the file.

Applying Translated Metadata to Translated Content

Unfortunately, translated metadata is ignored when importing XLIFF files. This section describes how to have translated metadata applied to the translated content.

Background Information

Although metadata exists in the XLIFF files, it does not appear in the content's metadata even if metadata is defined for that language. This is because metadata definitions have unique IDs across languages.

Note: While a content ID is the same for a corresponding content block in other languages, the same is not true for metadata.

As a result, the ID for the source language (for example, English) metadata is not automatically mapped to metadata for other languages (for example, Spanish).

To solve this problem, create a mapping between the IDs of metadata definitions of different languages that are synonymous. For example, consider the following metadata definitions.





Paper form number



Original page count



Número de papel de la forma



Cuenta de la página original



Estado de la minoría


In this example, IDs 102 and 106 are synonymous as are 104 and 108. Definition 110, however, only exists in Spanish.

The mapping is stored in an XML file. The mapping informs the XLIFF import process that metadata for ID 102 in English corresponds to ID 106 in Spanish and likewise with 104 and 108.

Setting up the Process to Apply Translated Metadata to Content

1. Open the folder site root/workarea/xslt/ and look for the file metadatadefinitions.xml. If it exists, go to step 2. If it does not, download it from Ektron at http://dev.ektron.com/uploadedFiles/DevCenter/Support/KB_Articles/XliffMetadata.zip.

The zip file includes modified XSLT files that access the XML file.

2. Create metadata definitions in the other language(s). Be sure to use the same data type.

To do this, log in, open the workarea, go to Settings > Configuration > Metadata Definition.

3. Make note of the definitions in the original language (for example, English).

4. Switch to view another language (for example, Spanish) and add a new definition. Assign it the same data type and other properties as the original. Make note of the new ID numbers.

Create metadata definitions in all languages you wish to support. You may add other languages and define more metadata definitions at any time.

5. Edit workarea/xslt/metadataDefinitions.xml. For each Metadata Definition, enter a <dd> element within the <dl> element. The <dd> element has the following form.

<dd title="Name of the metadata definition">
            <dfn id="ID" xml:lang="language-country code"/>
            <dfn id="ID" xml:lang="language-country code"/>

For example:

       <dd title="Paper form number">
            <dfn id="102" xml:lang="en-US"/>
            <dfn id="106" xml:lang="es-ES"/>
       <dd title="Original page count">
             <dfn id="104" xml:lang="en-US"/>
             <dfn id="108" xml:lang="es-ES"/>

The definition for ID 110 is not included because it applies to only one language.

Now that you have set up the xml file, the XLIFF import process accesses the metadataDefinitions.xml file to determine which definitions in the target language (for example, Spanish) correspond to the definitions in the source language (for example, English).

Visit the Ektron Dev Center at http://dev.ektron.com 1-866 - 4 - EKTRON

Ektron CMS400.NET Reference Version 8.02 SP1 Rev 1

Ektron Documentation,© 2011 Ektron, Inc.