Skip to main content
BOOK A DEMO

Provisioning of Language settings

skybow Support
  • Article Updated

Table of contents

The SharePoint multilingual feature allows users to create and manage multilingual sites, enabling viewing content to be shown in different languages based on a user’s preferred language settings. In the site language settings you can enable your site to use multilingual features and choose the languages you want to make available. 

skybow provides possibility to package and publish site language settings to the target site. You can manage packaging option in Language settings (in Solution Elements in solution studio). 

Language settings.png

Within Language settings you can package and publish configuration of site language settings, translation for navigation and modern pages, and localization of site UI elements for enabled alternative languages. These options can be published separately.  

Package & Publish Language Settings

To package and publish site language settings you need to do the following: 

  1. Navigate to the Language settings solution element in the solution studio.
  2. Check the checkbox 'Package site language settings'.  This option allows you to include configuration of the site language settings  (<site>/_layouts/15/muisetng.aspx)* in the package.
    *Replace <site> with your actual SharePoint site URL.
Language settings.png

Note: For the setting "Enable translation into multiple languages", skybow support package and publish site language configuration, translations of navigation and pages. Translations of site name, site description, footer, etc. are not supported to be provisioned.

Configure localization of site elements for SharePoint site include package & publish

To enable localization of UI site elements for alternative languages in SharePoint:

  1. Go to your SharePoint site.
  2. Navigate to Site Settings → Language Settings.
  3. Click Show advanced settings.
  4. Specify the languages that the site will support. Once configured, the SharePoint interface language will automatically adjust based on the user's browser language or Office 365 profile settings. 

skybow supports package and publish localization for alternative languages of the following UI elements:

  • List name;

  • Column display names (on the list level);

  • List content type name;

  • Site column name on the list level. 

    Example of localization of site elements for alternative language

    Default site Alternative language
    WineSellarEn.png
    WineSellarDe.png

To include localization of site elements for alternative language in the package:

  1. Open the Language Settings in the Solution Studio.
  2. Select languages you want to include localization for. To select language make sure this language is enabled in site language setting.

Note: 

  • Only languages supported by skybow will be packaged and published to the target site.
  • Each additional language may increase packaging and publishing time.
Language settings Localization.png

Note: In case during publishing you get the error on the validation step 'This language (<language name>) is not enabled on the target site and it is configured to be enabled by the Language setting' you can solve this by two ways: 

  • enable this language in site language settings and include in the package

  • go with Force update (overwrite all) publishing option and enabled needed language on the target site to apply this language

languageSettings_conflict.png

 

To add translation of the site elements into multiple languages you have to enable multilingual features in SharePoint:

  1. Go to your SharePoint site.
  2. Navigate to Site Settings → Language Settings.
  3. Toggle 'Enable translation into multiple languages' to on.
  4. Under the toggle add or remove site languages, click Save.
    Note: Assigned translators for the language are not supported to be package and publish

skybow supports package and publish translation for the following site elements:

  • Navigation

  • Modern Pages

Note: Once you add translations for modern pages you have to include translated pages into the solution, otherwise they won't be packaged and published to the target site.  

Related articles