SharePoint supported languages, language cultures and locale ids

Language Name
Culture Name
Locale ID
Arabic
ar-sa
1025
Bulgarian
bg-bg
1026
Catalan
ca-es
1027
Chinese (Simplified)
zh-cn
2052
Chinese (Traditional, Taiwan)
zh-tw
1028
Croatian
hr-hr
1050
Czech
cs-cz
1029
Danish
da-dk
1030
Dutch
nl-nl
1043
English
en-us
1033
Estonian
et-ee
1061
Finnish
fi-fi
1035
French
fr-fr
1036
German
de-de
1031
Greek
el-gr
1032
Hebrew
he-il
1037
Hindi
hi-in
1081
Hungarian
hu-hu
1038
Italian
it-it
1040
Japanese
ja-jp
1041
Kazakh
kk-kz
1087
Korean
ko-kr
1042
Latvian
lv-lv
1062
Lithuanian
lt-lt
1063
Norwegian (Bokmål)
nb-no
1044
Polish
pl-pl
1045
Portuguese (Brazil)
pt-br
1046
Portuguese (Portugal)
pt-pt
2070
Romanian
ro-ro
1048
Russian
ru-ru
1049
Serbian (Latin)
sr-latn-cs
2074
Slovak
sk-sk
1051
Slovenian
sl-si
1060
Spanish
es-es
3082
Swedish
sv-se
1053
Thai
th-th
1054
Turkish
tr-tr
1055
Ukrainian
uk-ua
1058
The Locale ID is important for SharePoint Solutions that deploy to the 15/16/Template/<locale id> folder, for example custom workflow activity .ACTIONS files.

The culture name is used in the names of resource files.

Comments

Post a Comment

Popular posts from this blog

Run Powershell script on Remote Computer/Server

Image
PowerShell Remoting allows you to run individual PowerShell commands or access full PowerShell sessions on remote Windows systems.   PowerShell is locked-down by default, so you’ll have to enable PowerShell Remoting before using it. This setup process is a bit more complex if you’re using a workgroup – for example, on a home network — instead of a domain.   Enabling PowerShell Remoting On the computer you want to access remotely, open a PowerShell window as Administrator – right click the PowerShell shortcut and select Run as Administrator.   To enable PowerShell Remoting, run the following command (known as a cmdlet in PowerShell):  Enable-PSRemoting -Force This command starts the WinRM service, sets it to start automatically with your system, and creates a firewall rule that allows incoming connections. The -Force part of the command tells PowerShell to perform these actions without prompting you for each step     Workgroup ...
Read more

Power BI Refresh Issue: unable to convert the value '' from the source data type 'VT_BSTR' to the expected data type 'VT_I8.

Image
While scheduling refresh in Power BI, you might get below error . Issue: Unable to convert the value '<pii></pii>' from the source data type 'VT_BSTR' to the expected data type 'VT_I8 .     Cause/Reason Behind: Column datatype mismatch between power bi desktop and power bi cloud report. Solution: Edit query in power bi desktop and change the data type so it’s in sync with Power BI service/cloud. Example: In my case, I have modified a column’s datatype from decimal to whole number (to display no. of days). Now power bi desktop and power bi service synced up and I could perform automatic data refresh.
Read more

SPDActivities - DP.SharePoint.Workflow - Workflow failed to run

Image
One of my SP 2016 application is using SPDActivities of Email extended feature of DP.SharePoint.Workflow to provide custom "From" address. But customers started to complain that they are not getting reminder emails anymore. Find below my STAR analysis, Situation : Recently I was facing an issue - Approval workflow failed to run. Customers not getting reminder emails anymore. Task : - Planned to look into SharePoint services, IIS site, web.config files (WFE and App Server), Latest patch/MS update/CU, Users permission. Analysis : Started looking into each below items,  - SharePoint Timer Service and Administration services were running and good - Account which is running the workflow got required permission - DP.SharePoint.Workflow got activated for the web application - Checked into web.config file in WFE server and App Server for below sections Under <SafeControls> below 3 lines need to added both in WFE and App server web.config files, ...
Read more