{"id":6379,"date":"2013-02-18T00:00:00","date_gmt":"2013-02-18T00:00:00","guid":{"rendered":"https:\/\/www.globalizationpartners.com\/2013\/02\/18\/website-translation-for-microsoft-sharepoint\/"},"modified":"2019-01-21T21:53:03","modified_gmt":"2019-01-21T21:53:03","slug":"website-translation-for-microsoft-sharepoint","status":"publish","type":"post","link":"https:\/\/www.globalizationpartners.com\/2013\/02\/18\/website-translation-for-microsoft-sharepoint\/","title":{"rendered":"Website Translation for Microsoft SharePoint"},"content":{"rendered":"

SharePoint is a Microsoft platform launched in 2001 and designed primarily to handle intranet documentation management tasks. Over time SharePoint functionality has been extended to handle not only intranet but also internet related content management tasks and content localization becomes a very important requirement to handle clients’ needs all over the world.<\/p>\n

SharePoint language packs<\/h4>\n

In order to enable SharePoint multilingual features, the first step is to download and install the language pack of the target languages from the Microsoft Download Center<\/a>:<\/p>\n

\"sharepoint-languages\"<\/p>\n

Language packs allow the creation of multilingual websites without need for a separate instance of SharePoint platform to be installed per language. By installing a language pack on a web server, administrators can create websites based on the language-specific templates which include the localized strings. Thus, deployment of a multilingual SharePoint website is made easy by deploying the multilingual website from one SharePoint platform.<\/p>\n

How SharePoint handles multiple languages<\/h4>\n

By default, SharePoint uses the default language of the installed SharePoint version but administrators can set a different language for a website and the platform can recognize the selected language by its ID.<\/p>\n

In SharePoint 2013, even if a language pack for a target language, such as Arabic, is installed and selected some user-interface items are not displayed in that language (e.g. warnings, errors, dialogs, etc.). For these types of elements, SharePoint depends on other technologies to handle them such as .NET Framework, ASP.NET, SQL SERVER, among others.<\/p>\n

Localizing SharePoint features using Microsoft Visual Studio<\/h4>\n

A multilingual SharePoint solution should cover different areas of the platform such as Features, WebParts, ASPX interface pages and functional code because all of these items are providing output for users. SharePoint uses the Resources File<\/em>, which is a repository to store localized strings in different languages following a standard naming convention (for example: base name such as SiteResource.resx<\/strong> and a culture-specific code such as se-SE).<\/p>\n

\"Page2\"<\/p>\n

Furthermore, in SharePoint Resource Files<\/em> should be found in a specific location based on usage. The following are the available locations to store Resource files:<\/p>\n

1.\u00a0 TemplateFeatures<Feature Name>Resources<\/em><\/p>\n

2.\u00a0 Resources<\/em><\/p>\n

3.\u00a0 ConfigResources<\/em><\/p>\n

4. <Virtual Directory>App_GlobalResources<\/em><\/p>\n

SharePoint Features<\/strong> can be localized in visual studio by selecting the Feature Resource<\/em>, then select Add Resource Feature<\/em>, then select Culture<\/em>:<\/p>\n

\"Page<\/p>\n

Once done, a resource file will be created for that feature. You can then open the resource files, add Keys<\/em> and from the Manifest<\/em> you can add the Key Values<\/em>.<\/p>\n

\"Page<\/p>\n

To add new Culture, the above steps should be repeated again for the new one. It is not possible to copy the resx<\/strong> file and rename it like the case in asp.net<\/strong> websites.<\/p>\n

SharePoint WebParts<\/strong> can be localized using the following steps:<\/p>\n

– Add \u00a0anew Mapped Folder<\/em> to the solution and from next screen select the Resource Folder<\/em><\/p>\n

\"Page<\/p>\n

– Right click the Resources<\/em> folder, add new item, select Resource File<\/em>.<\/p>\n

– Finally add your localized strings into the new Resource File<\/em> you just created:<\/p>\n

\"Page<\/p>\n

SharePoint ASPX pages<\/strong> are localized by setting a specific Resource File<\/em> within the page and then point the page to the correct file to retrieve the localized content using the following structure: <%Resources: Resource file name, Resource Key %>.<\/em> In order to able to use the the resource file in the above expression, the resx<\/strong> file should be located at the App_GlobalResources<\/em> folder of the application.<\/p>\n

SharePoint Custom Code<\/strong> can be localized by accessing the Global resource files using syntax listed below and by setting the method parameters such as Resource<\/em> and Key Names<\/em>.<\/p>\n

\"Page_3_4\"<\/p>\n

SharePoint localization best practices<\/h4>\n

In addition to the techniques used above, there are a number of best practices that can be employed to optimize the content localization process.<\/p>\n

– Prior to developing a multilingual Sharepoint website, establish a clear design vision to facilitate the localization process. Specifically, determine what needs to be set up in the Sharepoint Features architecture and flowchart a best localization approach (for example: using Global Resource Files<\/em> or a local resource).<\/p>\n

– Create clear separation between Code and Interface.<\/p>\n

– Externalize all static content like labels,link names, page titles, and descriptons<\/p>\n

– Implement a good routine to handle URLs between languages.<\/p>\n

– Engage a professionl globalization consultant to review all of the internationalization factors are present to faciliate the localization process for the website.<\/p>\n","protected":false},"excerpt":{"rendered":"

SharePoint is a Microsoft platform launched in 2001 and designed primarily to handle intranet documentation management tasks. Over time SharePoint functionality has been extended to handle not only intranet but also internet related content management tasks and content localization becomes a very important requirement to handle clients’ needs all over the world. SharePoint language packs […]<\/p>\n","protected":false},"author":2,"featured_media":6380,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[16],"tags":[530,1475,64],"_links":{"self":[{"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/posts\/6379"}],"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\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/comments?post=6379"}],"version-history":[{"count":3,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/posts\/6379\/revisions"}],"predecessor-version":[{"id":15984,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/posts\/6379\/revisions\/15984"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/media\/6380"}],"wp:attachment":[{"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/media?parent=6379"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/categories?post=6379"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.globalizationpartners.com\/wp-json\/wp\/v2\/tags?post=6379"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}