Microsoft SharePoint 2013 -
Multilingual
Verified Against Build #15.0.4128.1014
Prepared by
Sriram Bala
SharePoint Practice
Authentication Methods
2
Table of Contents
Plan for multilingual sites in SharePoint 2013 ................................................................................................................................... 3
About SharePoint multilingual sites .................................................................................................................................................. 3
Determine language and locale requirements .............................................................................................................................. 4
Determine language pack requirements ......................................................................................................................................... 4
Available language packs.................................................................................................................................................................. 6
When language packs are required .............................................................................................................................................. 9
Decide whether to use site variations............................................................................................................................................... 9
Create a multi-language website ......................................................................................................................................................... 10
Terminology ............................................................................................................................................................................................ 11
How variation sites work..................................................................................................................................................................... 12
Determine how pages are rolled out to sites ............................................................................................................................. 13
Create labels for source and target sites ...................................................................................................................................... 14
Create a variation site hierarchy ...................................................................................................................................................... 17
Author and publish ............................................................................................................................................................................... 17
Source site ribbon options ............................................................................................................................................................ 17
Target site ribbon options ............................................................................................................................................................. 19
List variations .......................................................................................................................................................................................... 21
Multilingual Reference ............................................................................................................................................................................. 22
Authentication Methods
3
Plan for multilingual sites in SharePoint 2013
SharePoint 2013 and SharePoint Online have features that enable you to support users in different regions or users who
speak different languages. You can use these features to create websites in different languages, or to enable users to view
sites in their preferred language. This article describes how to plan for multilingual sites in SharePoint 2013.
Topics




About SharePoint multilingual sites
Determine language and locale requirements
Determine language pack requirements
Decide whether to use site variations
About SharePoint multilingual sites
The SharePoint 2013 multilingual sites feature enables you to work in more than one language, to provide content to
users in more than one language, or both. By using the multilingual sites feature, you can do the following:




Create, manage, and read content in different languages.
Navigate a site in a preferred language.
Collaborate with people in different regions, in different languages, in the same application.
Manage personal sites by using a preferred language.
Search and browse content across a company by using a preferred language.
There are three ways that you can provide multilingual sites for users:1.
You can create sites in languages different from the one that was used to install SharePoint.
This option creates a site in which the site user interface appears in the language that was selected when the site
was created. For example, if the English version of SharePoint was installed, but Japanese is selected when the site
is created, the site user interface will appear in Japanese. This option only affects the site administration pages and
user interface, and does not affect content created on the site.
2.
You can use the multilingual user interface to enable users to view the site user interface in their preferred
language.
This option creates a site in one language, but can show the site user interface in another language, based on the
preferred language of the user. For example, if the site was created in English, but the user's preferred language is
Spanish, and the Spanish language pack was installed and enabled for the site, the site user interface for that user
will appear in Spanish. This option only affects the site administration pages and user interface, and does not
affect content created on the site.
3.
You can use the variations feature to make publishing content available in different languages on different
sites.
This option creates a source variation site that is used to author content in one language, and then syncs that
content to one or more target variation sites where it can be translated and consumed in other languages. For
example, you can author and publish content in English for http://contoso.com/en, and use variations to sync
content to http://contoso.com/fr, where you can translate it to French and publish it. Unlike the first two options,
Authentication Methods
4
the variations feature does not affect site administration pages or the user interface; it affects only content. You
can create the variation sites in different languages, and you can enable the multilingual user interface for users
who create content for the variation sites.
If your organization supports users in different regions or users who speak different languages, you must determine what
your multilingual requirements are and plan for multilingual site deployment when you plan your overall site structure and
navigation. To determine your multilingual requirements, you must do the following:


Determine the languages and locales that you must support.
Determine the language pack requirements for sites and users.
Decide whether you want to use the variations feature.
Determine language and locale requirements
You might have to create sites in multiple languages for any of the following reasons:


You want to provide content to users in different regions or countries, and you want to provide content to each
region or country in its specific language.
You want to provide content to customers whose business spans many geographic areas.
You are required by government regulation or organizational policy to provide content in more than one
language.
When you plan multilingual sites, you should also consider which locales are necessary to support your sites. Locale is a
regional setting that specifies the way numbers, dates, and times are shown on a site. But locale does not change the
language in which the site is viewed. For example, selecting the Thai locale changes the default sort order of list items,
and uses the Buddhist calendar instead of the default calendar. But it does not change the site user interface language to
Thai. Locale is a setting that is configured independently of the language specified when a site is created. In your
spreadsheet, record any locales that you want to use with specific languages. The site locale can be changed, but only until
any of the lists on the site are indexed.
Determine language pack requirements
SharePoint language packs enable you to create site collections and sites in multiple languages without requiring separate
installations of SharePoint 2013. A farm administrator must install language packs on all front-end web servers in the
SharePoint farm before sites can be created in languages other than the default language.
When you create a site collection or a site and select a language, the user interface text that appears on the site collection
or site is shown in the selected language. For example, when you create a site in French, the toolbars, navigation bars, lists,
and column headings for that site appear in French. Likewise, if you create a site in Arabic, the site administration pages
and user interface, such as toolbars, navigation bars, lists, and column headings for that site, appear in Arabic, and the
default left-to-right orientation of the site changes to a right-to-left orientation to correctly show Arabic text.
Authentication Methods
5
If your site will have users who can't work in the default language that you plan to use for the site, you should install
language packs that will enable users to work in their preferred language by using the multilingual user interface. If you do
not provide support for additional languages, users might find it difficult to use site features in their non-native language.
Language packs provide language-specific translation of user interface elements such as the following:





Site administration pages
Ribbon elements
List and site column headers
Site settings interface
Templates for new lists, document libraries, and sites
Managed metadata term sets and terms
What is a site's 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:







Web parts
Site title and description
SharePoint default menus and actions
Default columns
Custom columns (list or site)
Navigation bar links
Managed metadata services
Use MUI when you want to create sites, site collections, or Web pages in a language other than the default language for
your installation, or, if your site will have users who cannot work in the default language that you plan to use for the site.
1.
From a site page, click the icon for Settings
, and then click Site Settings.
2.
On the settings page, in the Site Administration section, click Language Settings.
3.
In the Alternate Language section, check the checkbox for the languages you want users to be able to use to
display their user interfaces. For example, if the only language pack installed is French, then French is the only
alternate language available for you to select.
4.
Click OK.
5.
Now your users can change the display language for their personal use of the user interface;
Authentication Methods
6
Based on the language requirements of your site collections or sites, determine the language packs that must be installed
on every front-end web server.
Available language packs
Language
Language
ID
SharePoint
Foundation 2013
SharePoint Server
2013
SharePoint
Online
Arabic
1025
Yes
Yes
Yes
Basque (Basque)
1069
Yes
Yes
Yes
Bulgarian
1026
Yes
Yes
Yes
Catalan
1027
Yes
Yes
Yes
Chinese
(Simplified)
2052
Yes
Yes
Yes
Chinese
(Traditional)
1028
Yes
Yes
Yes
Croatian
1050
Yes
Yes
Yes
Czech
1029
Yes
Yes
Yes
Danish
1030
Yes
Yes
Yes
Dutch
1043
Yes
Yes
Yes
English
1033
Yes
Yes
Yes
Estonian
1061
Yes
Yes
Yes
Finnish
1035
Yes
Yes
Yes
French
1036
Yes
Yes
Yes
Authentication Methods
7
Galician
1110
Yes
Yes
Yes
German
1031
Yes
Yes
Yes
Greek
1032
Yes
Yes
Yes
Hebrew
1037
Yes
Yes
Yes
Hindi
1081
Yes
Yes
Yes
Hungarian
1038
Yes
Yes
Yes
Indonesian
1057
Yes
Yes
No
Italian
1040
Yes
Yes
Yes
Japanese
1041
Yes
Yes
Yes
Kazakh
1087
Yes
Yes
Yes
Korean
1042
Yes
Yes
Yes
Latvian
1062
Yes
Yes
Yes
Lithuanian
1063
Yes
Yes
Yes
Malay (Malaysia)
1086
Yes
Yes
No
Norwegian
(Bokmål)
1044
Yes
Yes
Yes
Polish
1045
Yes
Yes
Yes
Portuguese
(Brazil)
1046
Yes
Yes
Yes
Portuguese
(Portugal)
2070
Yes
Yes
Yes
Romanian
1048
Yes
Yes
Yes
Authentication Methods
8
Russian
1049
Yes
Yes
Yes
Serbian (Cyrillic)
3098
Yes
Yes
No
Serbian (Latin)
2074
Yes
Yes
Yes
Slovak
1051
Yes
Yes
Yes
Slovenian
1060
Yes
Yes
Yes
Spanish
3082
Yes
Yes
Yes
Swedish
1053
Yes
Yes
Yes
Thai
1054
Yes
Yes
Yes
Turkish
1055
Yes
Yes
Yes
Ukrainian
1058
Yes
Yes
Yes
Vietnamese
1066
Yes
Yes
No
Authentication Methods
9
When language packs are required
To do the following
Are language packs required?
Create sites in different languages.
Yes
Enable the multilingual user interface on sites.
Yes
Use the variations feature to create multilingual content.
No
Create variation sites in different languages.
Yes
Enable the multilingual user interface on variation sites.
Yes
Decide whether to use site variations
The SharePoint Server 2013 variations feature enables site owners to make the same content available to specific
audiences across different sites by maintaining customizable copies of the content from the source variation site in each
target variation site. For a multilingual site, you might want to use the primary language of your organization as the source
variation site. You can create the target variation sites in the same language as the source variation site, or in the language
the target variation site is intended to support. If you plan to create the target variation sites in other languages, verify that
the corresponding language packs are installed.
When you plan for multilingual sites, consider whether you have to create content that will be shared across sites, but
must be changed to meet regional requirements or translated to meet language requirements. If you think there is a
possibility that you might have to set up variations sites, you should plan for them beforehand. It is very difficult to
integrate variations sites into a site collection after the site structure is implemented. The following factors can affect your
ability to easily move to using variations sites later in the life of your site:
Custom code Code that contains references to the location of the root variations site.

Site customizations Site navigation, Master Pages, and other customizations.

Search Search scopes must be created for each variation label, and the site properties of each variations site
must be changed.
If you plan to translate content on your variations sites, you must decide whether to use human translation or machine
translation. If you plan to use machine translation, make sure that the language to which you want to translate content is
available for the Machine Translation service.
Authentication Methods
10
Create a multi-language website
A multi-language site is a single website that’s reproduced and published in more than one language. Most of the content
on the site is the same but is localized to reflect the language and culture of customers in various regions. As you can
imagine, producing and maintaining a website with multiple language variants can be difficult and time-consuming.
The SharePoint Online variations feature helps to simplify the task by automating page and site creation for each language
and locale. It uses a source-target paradigm that enables you to author once and publish broadly with minimal setup time.
In this article
o
o
o
o
o
o
o
Terminology
How variation sites work
o Activate publishing on the site collection
Determine how pages are rolled out to sites
o Configure variation settings
Create labels for source and target sites
o Create the source variation site
o Create target variation labels
Create a variation site hierarchy
o Create the hierarchy
o Check status in the variation log
o Add a new variation site to an existing site hierarchy
Author and publish
o Source site ribbon options
o Update all targets
o Specify which targets should receive updates
o Target site ribbon options
o View changes from the source
o Accept changes from the source
o Reject changes from the source
o Package a page for translation
o Upload a translated package
o Submit a page for machine translation
o Check translation status
List variations
o Specify which targets should receive list updates
Authentication Methods
11
Terminology
Before setting up your multi-language website, it’s helpful to understand the SharePoint Online variations terminology.
This table defines key terms you will encounter in the variations setup and management process.
TERM
DEFINITION
Variations
Individual instances of a website that are localized and/or translated for a particular language and
locale.
Variation
The base URL for all variations of your website. Generally found at the root of the site collection, the
home
variation home can also be a subsites in a collection. It redirects site visitors to the appropriate
variation site based on browser location settings.
Variation
The language-locale pair for a variation site and the identifier for the top-level variation site and all
label
sites, content, and so forth, under the top-level site. For example, the label en-us means the site is
published in English and displayed to users whose location, according to their browser settings, is the
United States. Conversely, en-uk means the site is published in English and displayed to users whose
browser settings indicate United Kingdom. The label is included in the site URL and might look
something like this: http://contoso.com/en-us.
Source
The site where content is authored and published. From this source, all variation sites will be copied.
variation
Once a site has been identified as the source, it cannot be changed, and no other sites within the site
site
collection can be designated as the source.
Target
Sites that receive most of their content from the source variation site. New content can be created on
variation
a target variation site, but that content is not shared with other sites and is unique to the site on
site
which it was created.
Variation
The complete set of variation sites, including the source.
hierarchy
Variation
Publishing pages that are stored in the Pages library of the source and target variation sites.
pages
Microsoft
The service used by SharePoint for machine translation of website content. The Microsoft Translator is
Translator
a webpage widget that allows you to translate pages on your website in real time. Users can see your
pages in their own language without having to go to a separate translation website to share your
page with others in multiple languages.
Authentication Methods
XLIFF File
12
A standard XML-based format that is supported by a wide range of localization tools.
TOP OF PAGE
How variation sites work
At its core, a variation site is a managed copy of a website. Authoring takes place in the source site, the site in your
variation hierarchy from which all others are copied. When you publish the source site, all publishing pages from the
Pages library are replicated automatically on the targets and queued for translation and publishing. Document libraries,
announcement lists, and image libraries are also replicated as part of the variations process.
Variation sites are built hierarchically with the root site at the top and all language variants beneath it. The source and
targets sit one level below the root. Here’s an example:
The variations feature is a component of the SharePoint Online publishing infrastructure, and it uses publishing site
templates when creating sites. The actual content publishing process, however, depends on which site template you
choose when setting up your variations.
Selecting Publishing Site for the source variation means that all pages on the source or below it in the site hierarchy must
be published before they are replicated on target variation sites. Choosing Publishing Site with Workflow means pages
Authentication Methods
13
must go through the approval workflow before being replicated on target variation sites. A variations timer job does the
work of replicating approved and published pages to target sites, and is kicked off once the site hierarchy is created.
Because the variations feature is dependent on the publishing infrastructure and the publishing site templates, you’ll have
to enable publishing on your site collection before creating variation labels or a site hierarchy.
Activate publishing on the site collection
1.
From the root of your site collection click Settings
, and then click Site settings.
2.
On the Site Settings page, under Site Collection Administration, click Site collection features.
3.
Scroll down to SharePoint Server Publishing Infrastructure, and then click Activate.
Once publishing is enabled, you will follow a four-step process to set up variations, as follows:
1.
Determine how pages are rolled out to variation sites.
2.
Create labels for source and target sites.
3.
Create the variation hierarchy.
4.
Author and publish.
Determine how pages are rolled out to sites
You’ll want to give some thought to how your organization will handle automatic site creation, keeping in mind that you
have some flexibility in deciding what content gets published and when. For example, let’s say your company has just
launched a new product and features it prominently on the home page of your website. It should be featured on the
websites of all your international subsidiaries as well, but since the product won’t be released internationally for several
more months, you want site owners in each of the subsidiaries to hold back the content until the product is available
locally. By adjusting the variations settings, you can control how new, updated, and deleted pages are handled on each
variation site.
Configure variation settings
NOTE
Only site collection administrators can perform this action.
1.
From the root of your site collection, click Settings
, and then click Site settings.
2.
On the Site Settings page, under Site Collection Administration, click Variations Settings.
3.
In Site, List, and Page Creation Behavior, select:
Create Everywhere if new pages should be copied to all targets.
Authentication Methods
14
-orCreate Selectively if you want to choose which targets should receive new pages.
4.
In Recreate Deleted Target Page, select:
Recreate a new target page when the source page is republished if you want the new page to replace one that has
been deleted.
-orDo not recreate a new target page when the source page is republished if you don’t want the new page to replace
one that has been deleted.
5.
In Update Target Page Web Parts, select:
Update Web Part changes to target pages when variation source page update is propagated if you want web
part changes on the source to be updated on the target. Any web part customizations on the target will be lost.
-orDo not update Web Part changes to target pages when variation source page update is propagated if you don’t
want web part changes on the source to be updated on the target.
6.
In Notification, select the check box to alert site owners when new pages or page updates are available.
7.
Click OK.
Create labels for source and target sites
A variation label is the language-locale pair for a variation site, such as en-us, de-de, or fr-fr. This label is included in the
site URL.
The first label you’ll need to create is the source label. The source is where you author the content that will be copied to
target sites. For a multi-language site, you might want to use the primary language of your organization as the source
label.
NOTE
There can be only one source label, and after you’ve specified the source label, you cannot change it to another
one without deleting the source label and breaking all existing source-target relationships.
Create the source variation site
The next step is to create the target labels, one for every language variant in the hierarchy. For example, if you intend to
publish four language variations of your site (a source and three targets), you will create four labels—one for each
language.
1.
From the root of your site collection, click Settings
, and then click Site settings.
2.
On the Site Settings page, under Site Collection Administration, click Variation labels.
Authentication Methods
15
3.
On the Variations Label page, click New Label.
4.
On the Create Variation Label page, in Site Template Language, select the language to be used in the multilingual
user interface (MUI) of the source site. The choice is based on which language packs are available with your Office 365
subscription. Language packs are needed only if you want to use MUI for the administrative pages of the site.
Language packs are not required for variations.
5.
In Locale, select the language and locale pair to be used for this site. The locale determines the language for all usergenerated content; formatting for items such as date, time, and currency; and the method for redirecting users from
the root site, according to their browser settings.
6.
In Location, type the location of the source and targets within your site hierarchy. It they will be at the top level of the
site collection, just type a forward slash (/).
7.
In Label Name, the language-locale pair is entered for you based on the locale chosen earlier. You can edit this
information.
8.
In Description, type a description to help users understand the purpose of the label. For example, you might type
“English.”
9.
In Display Name, the language and locale are entered for you based on the locale you selected earlier. You can edit
this information.
10. In Publishing Site Template, select the site template to use for each variation site. Select Publishing Site with
Workflow if you want all pages to go through an approval workflow before being copied to target variation sites.
Select Publishing Site if an approval workflow isn’t necessary. All pages on the source or below it in the site hierarchy
must be published before they can be copied to target variation sites.
11. In Label Contact, type the email addresses of those people who should receive notification when the source variation
site is created.
12. Click OK. The process of creating a source begins automatically.
Create target variation labels
It is not necessary to create all target variations at once. In fact, we recommend that you create content on the source
before creating target labels. We also recommend that you create multiple target labels before creating the site hierarchy.
1.
From the root of your site collection, click Settings
, and then click Site settings.
2.
On the Site Settings page, under Site Collection Administration, click Variation labels.
3.
On the Variations Label page, click New Label.
4.
In Site Template Language, select the language to be used in the MUI of the source site. The choice is based on
language packs installed. Language packs are needed only if you want to use MUI for the administrative pages of
the site. Language packs are not required for variations.
Authentication Methods
5.
16
In Locale, select the language and locale pair to be used for this site. The locale determines the formatting for
items such as date, time, and currency, as well as how users are redirected from the root site, according to their
browser settings.
6.
Click Continue.
7.
In Label Name, the language-locale pair is entered for you based on the locale chosen earlier. You can edit this
information.
8.
In Description, type a description to help users understand the purpose of the label. For example, you might type
“English.”
9.
In Display Name, the language and locale are entered for you based on the locale you selected earlier. You can
edit this information.
10. In Hierarchy Creation, select the portion of the source that you want copied to this new target:
11. Publishing Sites, Lists with Variations, and All Pages to create a hierarchy of publishing sites and all pages.
12. Publishing Sites Only to create a hierarchy of publishing sites only.
13. Root Site Only to create a top-level site with no sites or pages.
14. Click Continue.
15. In Create Translation Package, select whether to allow human translation of the content on this target. Enabling
this option means that content will be packaged into an XLIFF file, which is downloaded onto your computer so it
can be sent to translators for processing. An XLIFF file is a standard XML-based format that is supported by a wide
range of localization tools.
16. In Machine Translation, select whether to allow machine translation on this target. Enabling this option means that
users can request translation through the Microsoft Translator service.
17. Click Continue.
18. In Page Update Behavior, select how you want existing pages to be updated when changes come from the source:
19. Users can manually sync updates from source variation pages to let site owners or content authors compare
the updated page with the existing one and determine which changes to accept.
20. Automatically update target variation pages to send a draft version of the page to the target.
21. In Label Contact, type the email addresses of those people who should receive notification when the target
variation site is created.
22. Click Continue.
23. Review your label settings, and then click Finish.
Authentication Methods
17
Create a variation site hierarchy
Creating the variation site hierarchy accomplishes two tasks:
o
o
Associates variation source and targets with one another and with the variation root site.
Creates the sites and pages for each language variation.
Creating the variation site hierarchy can be resource intensive, particularly if you have a lot of variations within your
hierarchy. Therefore, hierarchy creation is handled as part of a bulk timer job that runs approximately every hour. You can
monitor the progress of your timer job by checking the variations log.
Create the hierarchy
1.
From the root of your site collection, click Settings
, and then click Site settings.
2.
On the Site Settings page, under Site Collection Administration, click Variation labels.
3.
Click Create Hierarchies.
Check status in the variation log
1.
From the root of your site collection, click Settings
, and then click Site settings.
2.
On the Site Settings page, under Site Collection Administration, click Variation logs.
Add a new variation site to an existing site hierarchy
After you create the variation site hierarchy, you can add a new target site at any time.
1.
From the root of your site collection, click Settings
, and then click Site settings.
2.
On the Site Settings page, under Site Collection Administration, click Variation labels.
3.
Click New Label, and then create the label as described in "Create target variation labels" above.
4.
Repeat steps 1 and 2 for each new target, and then click Create Hierarchies.
Author and publish
Once the variation hierarchy is created, new variations and translation options will appear on the ribbon. The exact options
available depend on whether you’re working on a source or target site.
Source site ribbon options
On the Publish tab of the ribbon on the source site you’ll see a new group called Variations. Here you’ll find two buttons
that control how content updates will be distributed to target sites.
Authentication Methods
18
BUTTON
DESCRIPTION
Create new
Establishes a relationship between source and target. Targets receive a copy of the source page and
target
any future updates to it.
Update all
Copies the current version of the source to all existing targets. The page remains as an unpublished
targets
draft until the variation site owner or author publishes it.
Update all targets
1.
From the source site, browse to the new or updated page. (The page must be published or approved via approval
workflow before it can be copied to targets.)
2.
On the Publish tab, in the Variations group, click Update all targets. Note that content can be copied only from
source to target and not from target to target.
Specify which targets should receive updates
1.
From the source site, browse to the new or updated page. (The page must be published or approved via approval
workflow before it can be copied to targets.)
2.
On the Publish tab, in the Variations group, click Create new target.
3.
On the Create Variation page, select the check box next to each target that should receive the content. To send the
content to all available targets, select the check box next to Label. Note that content can be copied only from source
to target and not from target to target.
4.
Click Continue.
Authentication Methods
19
Target site ribbon options
Target site owners receive a notification when new content arrives from the source. The notification sits at the top of the
affected page and includes a link that takes them to the source so they can review the extent of changes and determine
whether to accept or reject them. The amount of leeway for accepting and/or rejecting new and updated content depends
on how the variation settings were configured by the site collection administrator.
The ribbon on each target site includes a Variations tab similar to the one shown below:
This tab helps you both review content received from the source and prepare it for either human or machine translation.
Each of the buttons is explained in the following table.
BUTTON
EXPLANATION
View Changes
Compares the source content just copied with the current translation on the target site. To
determine the scope of changes, click View Changes whenever you receive new content from the
source. If changes are minimal, you might elect to ignore them or make them by hand.
Sync from
Provides two options:
Source


Sync from Source copies the source content to the target site as an unpublished draft. Once
published, this draft overwrites the current target content.
Set as Current designates the target content as equivalent to the source content without accepting
Authentication Methods
20
updates. The appropriate choice when updating content by hand.
Create
Exports the current page as an XLIFF file on your computer, and notifies the people you designate
Translation
that the file is ready for translation. The XLIFF file has an .xlf extension. This feature was enabled or
Package
disabled during creation of the variation label.
Upload
Enables you to upload the translated XLIFF file and review the changes. This feature was enabled
Translation
or disabled during creation of the variation label.
Machine
Uses the Microsoft Translator for real-time translation, if enabled. This feature was enabled or
Translate
disabled during creation of the variation label.
Translation
A log of translation activity, including both human and machine translation.
Status
View changes from the source
1.
Browse to the page just received from the source.
2.
In the notification at the top of the page or on the Variations tab, click View Changes.
A new window opens with a report highlighting the differences between the most recently synchronized source and
the current source.
Accept changes from the source
1.
Browse to the page just received from the source.
2.
On the Variations tab, click Sync from Source.
The existing page is replaced with the one received from the source.
3.
When you’re satisfied with the changes, publish the page.
Reject changes from the source
1.
Browse to the page just received from the source.
2.
On the Variations tab, click Set as Current.
The existing page remains as is.
Authentication Methods
21
Package a page for translation
1.
Browse to the page whose content you want to translate.
2.
On the Variations tab, click Create Translation Package.
3.
Enter the email addresses of everyone who should be notified when the content is ready for translation. Each recipient
will get an email containing a link to the translation package.
Upload a translated package
1.
Browse to the page that has just been translated.
2.
On the Variations tab, click Upload Translation.
3.
Browse to the SharePoint library or other location on your computer or SharePoint site where the translated XLIFF file
is stored.
4.
Optional: For tracking purposes, enter the name of the company that did the translation.
5.
When you’re satisfied with the translation, publish the page.
Submit a page for machine translation
1.
Browse to the page whose content you want to translate.
2.
On the Variations tab, click Machine Translate.
The page is refreshed with the translated content.
3.
When you’re satisfied with the translation, publish the page.
Check translation status
1.
Browse to the page whose content is being translated.
2.
On the Variations tab, click Translation Status.
3.
Review the translation status log.
List variations
List variations are similar to page variations, with one exception: Only complete lists, and not individual list items, can be
replicated to target sites.
Authentication Methods
22
Specify which targets should receive list updates
1.
From the source site, browse to the new or updated list.
2.
On the Variations tab, click Settings.
3.
On the Create Variation page, select the check box next to each target site that should receive the list. To send the list to
all available targets, select the check box next to Label.
4.
Click Continue.
Multilingual Reference
Plan for multilingual sites in SharePoint 2013
http://technet.microsoft.com/en-us/library/cc262055(v=office.15).aspx
Create a multi-language website
http://office.microsoft.com/en-us/sharepoint-server-help/create-a-multi-language-website-HA102886546.aspx