11 September, 2012

Language Offerings for SharePoint 2010 Products


Multilingual support is key to the deployment success of many of our global customers. This post shares our plans for language coverage for SharePoint 2010 and estimated release timeframes. To date we have shipped 19 languages, including English, Japanese, French, Russian, German, Spanish, Chinese Simplified, Chinese Traditional, Arabic, Korean, Hebrew, Hindi, Danish, Thai, Swedish, Polish, Portuguese (Brazil), Dutch and Italian with 21 others shipping between now and September 2010.

The following table applies to SharePoint Foundation 2010, SharePoint Server 2010, Office Web Apps, Project Server 2010, Search Server 2010 and Search Server 2010 Express. The Estimated Release Timeframe is RTM date, which may be earlier than the date when it hit public download.

Note: Fast Search Server for SharePoint 2010 uses the language infrastructure of SharePoint Server 2010, so there is no separate language pack or localized version for it.

[ll: Language code. CC: Country Code. SKU: Stock Keeping Unit (The full release of the product). LP: Language Pack]

Language
ll-CC
Release Type
Estimated Release Timeframe
Arabic***
ar-sa
SKU and LP
Released
Basque**
eu-es
LP
September
Bulgarian*
bg-bg
LP
August
Catalan**
ca-es
LP
July
Chinese (Simplified)
zh-cn
SKU and LP
Released
Chinese (Traditional)
zh-tw
SKU and LP
Released
Croatian*
hr-hr
LP
August
Czech
cs-cz
SKU and LP
June
Danish
da-dk
SKU and LP
Released
Dutch
nl-nl
SKU and LP
Released
English
en-us
SKU and LP
Released
Estonian*
et-ee
LP
August
Finnish
fi-fi
SKU and LP
May
French
fr-fr
SKU and LP
Released
Galician**
gl-es
LP
September
German
de-de
SKU and LP
Released
Greek
el-gr
SKU and LP
July
Hebrew***
he-il
SKU and LP
Released
Hindi*
hi-in
SKU and LP
Released
Hungarian
hu-hu
SKU and LP
June
Italian
it-it
SKU and LP
Released
Japanese
ja-jp
SKU and LP
Released
Kazakh*
kk-kz
LP
August
Korean
ko-kr
SKU and LP
Released
Latvian*
lv-lv
LP
August
Lithuanian*
lt-lt
LP
August
Norwegian Bokmål
nb-no
SKU and LP
May
Polish
pl-pl
SKU and LP
Released
Portuguese (Brazil)
pt-br
SKU and LP
Released
Portuguese (Portugal)
pt-pt
SKU and LP
May
Romanian*
ro-ro
LP
July
Russian
ru-ru
SKU and LP
Released
Serbian Latin*
sr-latn-cs
LP
August
Slovak
sk-sk
LP
July
Slovenian
sl-si
LP
July
Spanish
es-es
SKU and LP
Released
Swedish
sv-se
SKU and LP
Released
Thai*
th-th
SKU and LP
Released
Turkish
tr-tr
SKU and LP
July
Ukrainian

Retain look up column values in export list template


It is known issues that on exporting list items, look up column values are lost.
If the list is very big, it might not be possible to fix that manually. This problem occurs since list template does look up on a table using GUID, on creating a list template and exporting to a different site, this GUID changes, hence it is no longer able to retain the values.


Suppose I have a list “Category” which has a look up column “sub category” which refers to list “Sub Categories”. I assume you have already created a look up listSub Categories” in the destination web.

  1. Browse to the source Web’s lookup list “Sub Category” and choose Modify settings and columns.
  2. Copy the source lookup list GUID from the URL.It should be a sequence of numbers and letters similar to:  %7BFFA47BF8%2D849C%2D4F20%2D9C50%2D173D2F5B6725%7D
  3. Browse to the destination Web’s lookup list and choose Modify settings and columns.
  4. Copy the destination lookup list GUID from the URL.Similar as point 2.
  5. Delete %2D from the string and replace with a dash sign (-). There should be no dash sign (-) at the start and the end. GUID should be in the following format: FA47BF8-849C-4F20-9C50-173D2F5B6725
  6. Save the source Web’s list that contains a lookup column “Category” to the lookup list as a list template called category.stp.
  7. Export the list template STP from the source list template gallery to the file system.
  8. Rename the category.stp file to category.cab so Windows can open it.
  9. Open the file, right click on the manifest.xml file and export it to the file system.
  10. Edit the manifest.xml file; find the source Web’s lookup list GUID and replace it with the destination Web’s lookup list GUID.
  11. Save the manifest.xml file.
  12. Open a VS.NET command prompt.
  13. Run the makecab command as: makecab manifest.xml category.stp
  14. Import the new STP into the destination Web’s list template gallery. You will need to delete it if it has previously been imported.