Take the community feedback survey now.


Dec 27, 2011
  5974
(0 votes)

An Overview of EPiServer Multilingual Capabilities

EPiServer CMS provides robust multilingual support that facilitates automatically rendering pages based on the URL, the language specified by the user, or the language detected from the user's browser settings.

With EPiServer CMS, multiple sites do not need to be created as multiple language variations can easily be managed on a single site. Authors can easily create or access all of the language variations of a page from any variation of the page.

 

Supported Languages for Web Site Visitors

The language support for your web site visitors is virtually unlimited. Any language can be supported as long as the language packs are installed on the web servers as part of the operating system. Language packs are included as part of the Windows operating system so there is no additional cost to add additional language support. EPiServer CMS is fully Unicode compliant.

 

Supported Languages for CMS Users

The EPiServer CMS interface (for content contributors and administrators) supports the following 12 languages out of the box:

  • English
  • Swedish
  • Danish
  • German
  • Spanish
  • French
  • Dutch
  • Norwegian
  • Portuguese
  • Finish
  • Chinese
  • Japanese

Additional language files can be created to support more languages. The text elements of the EPiServer CMS user interface are stored in XML language files.

Language support for your sites can be configured by administrators in “Manage Website Languages” and each CMS user can select their language in the “My Settings” section of EPiServer CMS as pictured below.

Figure1

Figure 1 – Language Support for Visitors and CMS Users

 

Language Settings

Administrators can specify which language variations can be created by content contributors, fallback languages that are to be displayed if the requested language variation does not exist, and replacement languages that are to override a specific language variation.

Figure2

Figure 2 - Language Settings

 

Side by Side Viewing and Editing

Content contributors can view and edit language variations of page side-by-side.

Figure3

Figure 3 - Editing Language Variations Side by Side

 

Notifications and Workflow

The "Ready for Translation" workflow reminds workflow participants to perform translations after a configurable interval and sends a final alert after a configurable interval to inform persons/groups if a page was not fully translated. This workflow can be configured to automatically start when the default language variation is changed and to assign translation activities to a unique translator for each variation.

Figure4

Figure 4 - Translation Workflow Configuration

 

Working with Translation Services

EPiServer TranslateX is an open source a module which enables you to export your entire site or a subset of pages to the XLIFF format, send it to a translation agency, and import the translations back EPiServer. TranslateX has two parts:

  • A core module that exports/imports pages from/to EPiServer CMS and activates the proper connector to start communication with the translation agency.
  • A connector module that handles communication between EPiServer CMS and the translation agency service. The default connector is XLIFF, where the translation tasks are created as XLIFF files

Figure5

Figure 5 - Creating a New Translation Project with TranslateX

Dec 27, 2011

Comments

Please login to comment.
Latest blogs
A day in the life of an Optimizely OMVP - Opticon London 2025

This installment of a day in the life of an Optimizely OMVP gives an in-depth coverage of my trip down to London to attend Opticon London 2025 held...

Graham Carr | Oct 2, 2025

Optimizely Web Experimentation Using Real-Time Segments: A Step-by-Step Guide

  Introduction Personalization has become de facto standard for any digital channel to improve the user's engagement KPI’s.  Personalization uses...

Ratish | Oct 1, 2025 |

Trigger DXP Warmup Locally to Catch Bugs & Performance Issues Early

Here’s our documentation on warmup in DXP : 🔗 https://docs.developers.optimizely.com/digital-experience-platform/docs/warming-up-sites What I didn...

dada | Sep 29, 2025

Creating Opal Tools for Stott Robots Handler

This summer, the Netcel Development team and I took part in Optimizely’s Opal Hackathon. The challenge from Optimizely was to extend Opal’s abiliti...

Mark Stott | Sep 28, 2025

Integrating Commerce Search v3 (Vertex AI) with Optimizely Configured Commerce

Introduction This blog provides a technical guide for integrating Commerce Search v3, which leverages Google Cloud's Vertex AI Search, into an...

Vaibhav | Sep 27, 2025

A day in the life of an Optimizely MVP - Opti Graph Extensions add-on v1.0.0 released

I am pleased to announce that the official v1.0.0 of the Opti Graph Extensions add-on has now been released and is generally available. Refer to my...

Graham Carr | Sep 25, 2025