{"id":6654,"date":"2012-06-27T00:00:00","date_gmt":"2012-06-27T00:00:00","guid":{"rendered":"https:\/\/www.globalizationpartners.com\/2012\/06\/27\/deploying-a-multilingual-website-with-episerver-part-1\/"},"modified":"2021-07-29T12:39:24","modified_gmt":"2021-07-29T12:39:24","slug":"deploying-a-multilingual-website-with-episerver-part-1","status":"publish","type":"post","link":"https:\/\/www.globalizationpartners.com\/2012\/06\/27\/deploying-a-multilingual-website-with-episerver-part-1\/","title":{"rendered":"Deploying a Multilingual Website with Episerver (Optimizely) (Part 1)"},"content":{"rendered":"

The Episerver (Optimizely) Web Content Management System 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 (Optimizely) can display the page content tree under different languages and also identify which pages have not been translated yet under a certain language.<\/p>\n

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.<\/p>\n

Setting up Episerver (Optimizely) for Multilanguage websites<\/h4>\n

In order to implement a website in different languages, you need to set up the following settings:<\/p>\n

– Enable Globalization in your Episerver (Optimizely) instance:<\/p>\n

(Admin mode -> Config Tab -> System Configuration -> System Settings > General Tab)<\/p>\n

\"0\"<\/p>\n

You also need to set the default language, which will be the one that is displayed when a visitor navigates the website. The default language is set up in the web.config<\/em> file, under the globalization tag.<\/p>\n

– Add the languages in which you are planning to translate your website.<\/p>\n

(Admin mode -> Config Tab –>Manage Website Languages)<\/p>\n

\"1\"<\/p>\n

In this page you have a list of all currently available languages and also a button to add more languages for website translation. Languages that are active in this list are available through the editor for content authors. On the other hand, the ones that are inactive will not allow new pages to be created, but the site will still show the pages previously created under that language.<\/p>\n

Language Settings (Fallback, Replacement)<\/h4>\n

– Another useful setting is the language fallback mechanism, where we can instruct Episerver (Optimizely) to fallback to a certain language when pages are not available in the languages the user is trying to reach.<\/p>\n

\"2\"<\/p>\n

Each available language in the site can have another available language as a default. For example, when we partially localize a website and we want one section to remain in the original language (English for example). This setting is quite useful by enabling the correct fallback configuration, and Episerver (Optimizely) will handle the rest automatically. To enable this feature, you can select Language Settings from the horizontal menu or by right click the page in the pages tree and selecting language settings.<\/p>\n

\"4\"<\/p>\n

\"5\"<\/p>\n

Select change; add alternative languages and select save.<\/p>\n

\"6\"<\/p>\n

Page Languages<\/h4>\n

You can manage languages for a specific page following the next steps<\/p>\n

– Select a page from the pages tree, right click, and select Page Languages.<\/p>\n

\"7\"<\/p>\n

– From the Action Window in the right column you can Create \/ Edit languages<\/p>\n

\"8\"<\/p>\n

Episerver (Optimizely) CMS provides different solutions to integrate external localization components through features like Plugins and Gadgets. GPI developed a component “GPI Connector” and integrated it as a Gadget in Episerver (Optimizely)’s latest version dashboard to support Episerver (Optimizely) localization process and to facilitate the translation by simply exporting content and re-importing the translation back to the CMS in a very easy and seamless way from inside the CMS.<\/p>\n","protected":false},"excerpt":{"rendered":"

The Episerver (Optimizely) Web Content Management System 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 (Optimizely) can display the page content tree under different languages and also identify which pages have not been translated […]<\/p>\n","protected":false},"author":13,"featured_media":6655,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[16],"tags":[530,284,1491,64],"_links":{"self":[{"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/posts\/6654"}],"collection":[{"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/comments?post=6654"}],"version-history":[{"count":7,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/posts\/6654\/revisions"}],"predecessor-version":[{"id":32563,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/posts\/6654\/revisions\/32563"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/media\/6655"}],"wp:attachment":[{"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/media?parent=6654"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/categories?post=6654"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/tags?post=6654"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}