Localization with EPiServer CMS Part 2

October 11, 2010

Multilingual content in EPiServer

EPiServer handles multilingual content in a very transparent way. Each localized page is not a separate entity, but a new version of the default language page. Using that mechanism, EPiServer can display the page content tree under different languages and also identify which pages have not been translated yet under a certain language.

Also, for each page type, you can define which properties/fields will vary depending upon the language. Properties that are unique per language are editable in all languages. On the other hand, properties that are the same across all the languages can only be edited in the default language.

Exporting and importing content for translation

There's no exporting/importing feature specifically designed for website localization shipped with EPiServer, but there's a module developed by one of their engineers that will facilitate this task. With that said, using EPiServer API it's quite simple to implement this yourself. Here at GPI we have created a piece of software ("connector") that implements these features and connects to our Globalization Project Management Suite® (GPMS), which enables a seamless connection to managing the localization process for a website.

Exporting content for translation

  1. When you are in Edit mode in EPiServer, for each page/node you'll have a "Translation tab" with a "New Project" button. Go to the top node of the section you want to export and click that button.
  2. Select the language(s) you want to translate and click "Include Subpages" if necessary.
  3. Click Next until the end of the wizard is reached and then close. There will be a new translation project created with the status "ReadyForSend".
  4. Since TranslateX runs in a different thread to not compromise the site, there's a "Translation Scheduler Service" option in Admin mode. The XLIFF files won't be created until that service runs (you can either configure to run automatically or even easier, click on the "Start Manually" button. That will create the XLIFF files in the folder you selected and will change the status of the translation project to ReadForImport.

Import translated content

  1. Go to the node were you created the translation project, and click on "Translation tab". Now the project will have an "Import" button that will launch the import wizard.
  2. Select the file to import and click Next.
  3. Select "New Version" and leave the other field empty. Click Next.
  4. Select the publish type that you need. In this case you would select "Publish" so you can review the translated site by browsing it. Click "Finish" to finish this step.
  5. If you browse the content in the selected language, you will be able to see the localized pages. And if you check the pages in the browser, you'll see that everything is pseudo-localized (everything that is stored in the EPiServer CMS).

Further GPI Resources on EPiServer Translation and Website Localization

Globalization Partners International (GPI) has previously localized and published several EPiServer web applications and presented detailed presentations and case studies about CMS and scalable website development. You may find many of the following references about website localization, globalization, development and EPiServer Localization:

Further Information on Localization Resources

Globalization Partners International (GPI) frequently assists customers with multilingual website design, development and deployment. A suite of globalization tools developed by GPI can empower you to achieve your multilingual project goals: you can explore them under the translation tools sections of our company website. GPI also offers localization services and internationalization, and can evaluate your application. Consider partnering with GPI prior to localizing or translating your application: this will help you avoid many mistakes and save considerable time and money on your localization projects.

Contact GPI for more information via e-mail at info@globalizationpartners.com, by phone at (866) 272-5874, or by requesting a free web development and  translation quote on your project.

Category:
Content Management Systems
Tags:
localization, CMS, Episerver, multilingual content, translation, website

Localization with EPiServer CMS Part 1What’s the difference between Translation Agency, Localization Services and LSP?

Comments

Currently, there are no comments. Be the first to post one!

Contact Us FREE Globalization eBooks Request Demo Request Quote


Ayman is a native Arabic speaker with extensive expertise in Arabic software and website localization. He is a Microsoft Certified professional (MCP) since 2001 and earned several certificates including MCSD, MCAD, MCTS and MCPD. He has over 12 years’ experience in software / websites engineering using Microsoft Programming tools including C#, ASP.NET, SQL Server, Visual Studio and other tools such as HTML, JavaScript, XML, Ajax and others.