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.
You can translate these kinds of Ektron information.
XLIFF (XML Localization Interchange File Format) is a format for exchanging localization data between participants in a translation project. This format lets translators concentrate on the text to be translated, without worrying about its layout. XLIFF is supported by a large group of localization service and tools providers. To learn more about XLIFF, visit these Web sites:
Ektron 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.
Trados is a commonly used translation tool. SDL Trados Studio 2009 supports XLIFF 1.1 and 1.2, which are recommended for use with Ektron.
If you are using Trados (an earlier version of the product), it only supports XLIFF 1.0. Note that Ektron 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.
Alternatively, select a Translation Package. See Also: Creating a Multilanguage Translation Package.
To create one or more .zip files for translation:
See Also: Using the Language Export Feature
Prerequisite: Only members of the Administrator User Group or those assigned to the XLIFF-Admin role can create, export, or import XLIFF files. See Also: Using the Roles Screens .
NOTE: The Include Subfolders field appears only if you click Export for Translation from the View Contents of Folder screen.
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.
The History section of the Export for Translation screen displays the translated files.
The history lists the .zip file created for each language. The top of the history window displays the most recently exported/imported files. ZIP files are indicated by the WinZip icon (). To the right of the icon are:
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 |
Pattern |
XLIFF |
item identifier[item ID]_[new language hexadecimal code][2 letter new language code].xlf
item ID varies, depending on whether the item is content, a form, a menu, or a menu item
|
ZIP |
xlf[timestamp in format yyyymmddThhmmss]_u[user ID] _ [new language hexadecimal code]-[2 letter language code].zip The user ID indicates which user performed the export or import. |
To import translated files into Ektron:
See Also: Using the Language Export Feature
Prerequisite: 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
IMPORTANT: Make sure the files have been translated before you import them.
For each new edition:
After you import the translation files, Ektron 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\.
Prerequisite: Member of Administrators group, or assigned to the Translation State Admin or XLIFF Admin role See Also: Defining Roles
Each Ektron content item has a translation status. Only content marked "ready for translation" is included when you create an .xlf file. Use Mark Translation Status on the View Content screen to mark the translation status. See Also: Content Statuses
The Mark Translation Status button may have any of 3 icons, which also indicate the content's status.
NOTE: You may apply this status to unapproved content if it needs translation before the site goes live.
If you click Mark Translation Status (), a menu appears that lets you change its status. Note that Export for Translation () appears on the toolbar only if the content's translation status is Ready for Translation.
If you create an .xlf file for a folder, only content whose translation status is ready is included in the file.
NOTE: The Localization Dashboard provides an overview of translation activity within Ektron.
The following metadata field names may be used for translation using the XLIFF export and import process.
This section describes how to have translated metadata applied to the translated content that does not use the above special names.
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. 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.
ID |
Name |
Language |
102 |
Paper form number |
en-US |
104 |
Original page count |
en-US |
106 |
Número de papel de la forma |
es-ES |
108 |
Cuenta de la página original |
es-ES |
110 |
Estado de la minoría |
es-ES |
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.
siteroot/workarea/xslt/
and look for metadatadefinitions.xml. If it exists, go to step 2. If it does not, download it from http://dev.ektron.com/uploadedFiles/DevCenter/Support/KB_Articles/XliffMetadata.zip. After unzipping the file, copy the .xslt files to the siteroot/workarea/localization/xliff
folder. Copy the xml file to the siteroot/workarea/xslt
folder.
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"/> : </dd>
For example:
<dl> <dd title="Paper form number"> <dfn id="102" xml:lang="en-US"/> <dfn id="106" xml:lang="es-ES"/> </dd> <dd title="Original page count"> <dfn id="104" xml:lang="en-US"/> <dfn id="108" xml:lang="es-ES"/> </dd> </dl>
The definition for ID 110 is not included because it applies to only one language.
Now, 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).