Introduction to multilingual features

If you are a site collection administrator, you are provided with two types of features to help you support users who speak different languages.

Multiple Language User Interface (MUI).    You use the MUI feature to create sites in different languages than the default language for your SharePoint installation, or to let individual users change the display language for their site’s personal user interfaces.

Variations (Enhanced to include change tracking.    You use the variations feature to create a source publishing Web site and then make copies of its content that can be translated into different languages. (The variations feature only works with publishing sites.)

Important:  Neither of these features is a translation tool. MUI changes the display language for the interface, and variations supports creating multiple versions of content that you can then have translated by localization professionals.

Note:  Do not assume that you have to create a Web site or a site collection in multiple languages because a document library contains documents in multiple languages. A document library can contain documents in multiple languages without requiring you to create Web sites or site collections in multiple languages.

In this article

Know the difference between a site’s user interface and content

User Interface

Content

When to use MUI, variations, or both features

Use MUI only

Use Variations only

Use both features together

Know the difference between a site’s user interface and content

Web sites generally have two parts: The user interface, which is how you interact with the site itself, and the content, which is the information that you keep on the site.

The MUI feature works with your site’s user interface, and the variations feature works with your site’s content.

User Interface

The user interface of your site refers to the elements on your screen that you use to interact with SharePoint, such as the menus, the navigation items, and the recycle bin.

With the MUI feature, you can display the following user interface elements in different languages:

  • Site title and description

  • SharePoint default menus and actions

  • Default columns

  • Custom columns (list or site)

  • Navigation bar links

  • Managed metadata services

Note:  The MUI feature only changes the display language for default UI elements. Custom UI elements that you have added are not translated.

Content

The variations feature works with your site content – the information you store on a site, but not the site user interface.

The basic content element that the variations feature works with is the page. It also copies folders, and can copy documents if they are linked to from a page that is on the variations source site. Variations doesn’t copy list items

When to use MUI, variations, or both features

Decide which multilingual features you are going to use before you begin creating your site collection, for the following reasons:

  • If you’re going to use the MUI feature, you’ll need to have your server farm administrator install the necessary language packs for every language you want to make available. After the farm administrator deploys language packs, site collection owners can create sites and configure the MUI to display the site user interface in different languages. Individuals can choose to view their sites in the language they want.

  • After you have created a site, you cannot change its default user interface language, so it’s important to start in the correct language.

  • If you’re going to use the variations feature, there are specific considerations about how you configure the sites for updating, notification, and other issues that you need to set before you create the sites.

Use MUI only

Use MUI only when you want to create sites, site collections, or Web pages in a language other than the default language, or, if your site will have users who cannot work in the default language that you plan to use for the site.

Use Variations only

Variations is designed to be used when your content has to be available to people who speak many different languages (or who might need to have specific information that is based on regional differences, on various mobile devices, or on corporate branding)—that is, Web sites that deliver tailored content to suit different cultures, different markets, and different geographic regions.

Also, if you are working in an environment where there are no language packs installed, you cannot use the MUI feature, but variations still allows you to set up a content distribution system for multiple languages.

Use both features together

When you are both publishing content to be translated into other languages, and you have site owners who might need to make changes to the site structure but who don’t speak the language that the site was created in, you can use both features together to make both the content and the UI of your sites available in multiple languages.

For example, using the variations feature, you might have created an English source site with a Chinese target. The variations feature sets up the Chinese site based on the language and locale settings. Now, imagine that a US-based site owner who does not speak Chinese needs to make some changes on the Chinese site for maintenance. Using the MUI feature, the English speaker can switch the Chinese site’s UI to English and more easily interact with the site.

Note:  When you are planning multilingual sites, you should also consider what locales are necessary to support your sites. Locale is a regional setting that specifies the way numbers, dates and times are displayed on a site. The locale setting does not change the language in which the site is displayed. For example, selecting the Thai locale changes the default sort order of list items and uses the Buddhist calendar instead of the default calendar. The locale is a setting that is configured independently of the language specified when a site is created, but unlike the language, the locale can be changed at any time.

Share Facebook Facebook Twitter Twitter Email Email

Was this information helpful?

Great! Any other feedback?

How can we improve it?

Thank you for your feedback!

×