Dec 27, 2011
  8592
(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

Jan 8, 2013 05:11 PM

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

Jeff Wallace
Jeff Wallace Feb 20, 2013 09:21 PM

Jonathan, I have not seen this yet.

Jul 4, 2013 10:56 AM

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

Jon

Please login to comment.
Latest blogs
Optimizely PaaS + Figma + AI: Auto‑Generate Blocks with Cursor

What if your design handoff wrote itself? In this end‑to‑end demo, I use an AI Agent (inside Cursor) to translate a Figma design into an... The pos...

Naveed Ul-Haq | Feb 5, 2026 |

Graph access with only JS and Fetch

Postman is a popular tool for testing APIs. However, when testing an API like Optimizely Graph that I will be consuming in the front-end I prefer t...

Daniel Halse | Feb 4, 2026

Best Practices for Implementing Optimizely SaaS CMS: A Collective Wisdom Guide

This guide compiles collective insights and recommendations from Optimizely experts for implementing Optimizely SaaS CMS, focusing on achieving...

David Knipe | Feb 4, 2026 |

A day in the life of an Optimizely OMVP: Learning Optimizely Just Got Easier: Introducing the Optimizely Learning Centre

On the back of my last post about the Opti Graph Learning Centre, I am now happy to announce a revamped interactive learning platform that makes...

Graham Carr | Jan 31, 2026

Scheduled job for deleting content types and all related content

In my previous blog post which was about getting an overview of your sites content https://world.optimizely.com/blogs/Per-Nergard/Dates/2026/1/sche...

Per Nergård (MVP) | Jan 30, 2026

Working With Applications in Optimizely CMS 13

💡 Note:  The following content has been written based on Optimizely CMS 13 Preview 2 and may not accurately reflect the final release version. As...

Mark Stott | Jan 30, 2026