Try our conversational search powered by Generative AI!

Joe Bianco
Dec 27, 2011
(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.


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.


Figure 2 - Language Settings


Side by Side Viewing and Editing

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


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.


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


Figure 5 - Creating a New Translation Project with TranslateX

Dec 27, 2011


Jonathan Graham
Jonathan Graham Jan 8, 2013 05:11 PM

Has anyone compiled a version of TranslateX for CMS version 7 yet?

Feb 20, 2013 09:21 PM

Jonathan, I have not seen this yet.

Jonathan Roberts
Jonathan Roberts Jul 4, 2013 10:56 AM

Can you let me know how you can do side by side editing in Episerver 6 R2 using Composer?
Many thanks


Please login to comment.
Latest blogs
Headless forms reloaded (beta)

Forms is used on the vast majority of CMS installations. But using Forms in a headless setup is a bit of pain since the rendering pipeline is based...

MartinOttosen | Mar 1, 2024

Uploading blobs to Optimizely DXP via PowerShell

We had a client moving from an On-Prem v11 Optimizely instance to DXP v12 and we had a lot of blobs (over 40 GB) needing uploading to DXP as a part...

Nick Hamlin | Mar 1, 2024 | Syndicated blog

DbLocalizationProvider v8.0 Released

I’m pleased to announce that Localization Provider v8.0 is finally out.

valdis | Feb 28, 2024 | Syndicated blog

Epinova DXP deployment extension – With Octopus deploy

Example how you can use Epinova DXP deployment extension in Octopus deployment.

Ove Lartelius | Feb 28, 2024 | Syndicated blog

Identify Azure web app instance id's for an Optimizely CMS site

When running Optimizely CMS in Azure, you will be using an instance bound cloud license. What instances are counted, and how can you check them? Le...

Tomas Hensrud Gulla | Feb 27, 2024 | Syndicated blog

Introducing Image Transformer - AI Assistant for Optimizely

We've got something super cool to share with you, and it's all about giving your images a fresh spin. Image Transformer, the latest feature from ou...

Luc Gosso (MVP) | Feb 26, 2024 | Syndicated blog