HomeDev GuideAPI Reference
Dev GuideAPI ReferenceUser GuideGitHubNuGetDev CommunityDoc feedbackLog In
GitHubNuGetDev CommunityDoc feedback

Optimizely Languages can be used to export and import XLIFF files that can be sent to inhouse translators or localization agencies.

`ITranslationPackageExporter` and `ITranslationPackageImporter` are interfaces used for import and export of translation packages to a project. The default implementations are `XLIFFTranslationPackageImporter` and `XLIFFTranslationPackageExporter`.

## Requirements

  • No additional license fee.

  • An Optimizely Content Management System (CMS) or Optimizely Customized Commerce installation.

  • See [Add-ons platform compatibility](🔗) for package and version information. 

## Install

  • Versions 7.5 and higher are [installed through NuGet](🔗).

  • Version 7 is installed and updated through one-click installation.

## Documentation

  • Developer guide:

    • [Configuring auto-translation](🔗)

    • [Breaking changes Optimizely Languages 2.0](🔗)

  • [User guide Optimizely Languages](🔗)

## Configure auto-translation

This section describes how to configure an auto-translation service for the Optimizely Languages app. Optimizely Languages uses as its translation provider Microsoft Translator, which is part of the Microsoft Cognitive Services collection of APIs, available in the [Azure portal](🔗). The following steps show how to configure the auto-translate option.

**Connect to the auto-translation service**

  1. [Subscribe to Azure](🔗), if you haven’t done so already.

  2. Configure the auto-translate component in Optimizely Languages.

    1. Go to admin view > **Config** > **Tool Settings** > **Language Manager**.

    2. In the **Translator Provider**, select **Cognitive Service Translator**.

    3. In the **Subscription Key** box, enter your Microsoft subscription key (Key 1).

    4. In **Subscription Region**, enter the Location value from the Azure subscription service.

    5. Save your changes.

See also: [Reminder: Move Translator API subscriptions from DataMarket to Azure before April 30, 2017](🔗).

## Breaking changes for Languages version 2

This topic describes API changes in version 2 of Episerver Languages.


Episerver Languages was renamed to Optimizely Languages.

### Changed

Introduced new methods in the `ILanguageBranchManager` interface and its implementation, `LanguageBranchManager`. Compared with old methods, the difference is that the new method returns newly created content as an `out` paramenter (`createdContentLink`):

### Marked as obsolete

The following functions in `ILanguageBranchManager` and its default implementation `LanguageBranchManager` are obsolete and will be removed in an upcoming release:

### New dependencies 

Languages 2.0 depends on newer packages: _EPiServer.CMS.Core_ 9.8, _EPiServer.CMS.UI_ 9.5.0