Try our conversational search powered by Generative AI!

Language for editor (UI) localized


1) Localizing content language(for web site visitors) and localizing editor UI language (for content editors). Are these two implemented differently in Episerver?

There are two ways to localize. 

2.1) Xml

What I do not understand is how to get the localized string when there are multiple languages mentioned here?

2.2) Localization service API

This is clear. But can this be used in localizing editor UI language (for content editors)?

The example for #2.1 

    Description = "This text can you have in XML instead"
public class StandardPage : PageData
            GroupName = SystemTabNames.Content,
            Name = "This text can you have in XML instead ",
            Description = " This text can you have in XML instead " 
        public virtual ContentArea MainContentArea { get; set; }	

      A description of the page type
          Name text from XML
          Description text from XML
Sep 13, 2017 9:01

Hi Sanjay,

EPiServer UI is using localization service under the hood. You can specify the language in the language node, as follows:

<language name="English" id="en">

The display attribute supports only one language (Name and Description values), so it's recommended to localize strings in the XML file(s) instead.

You can set up Alloy sample project, and take a look at XML files in Resources/LanguageFiles folder.

Edited, Sep 13, 2017 10:25

or use database driven localization provider instead of xml one ;)

Sep 15, 2017 17:30
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.