SharePoint Portal Server 2001 Scenario

SharePoint Portal Server 2001 supported six languages: English, French, German, Italian, Japanese, and Spanish. SharePoint Portal Server 2003 provides support for a total of 25 languages (including English).

When a SharePoint Portal Server 2001 administrator needs to support users with a language other than the original six supported languages, he or she usually installs the English language version of SharePoint Portal Server, and users use the local language version of Microsoft Office to create documents in their local language.

This scenario assumes there is an existing SharePoint Portal Server 2001 server installation and the workspace’s document library is used to store Microsoft Word documents primarily written in a language other than English (such as Korean). The language used on the workspace’s dashboard is English.

The goal of this scenario is to move the English workspace containing Korean Word documents to a SharePoint Portal Server 2003 solution that is entirely in Korean.

Migrating to SharePoint Portal Server 2003

Spout.exe and Spin.exe can be used to export and import the documents and associated descriptive information from the Web Storage System–based document library on the server running English SharePoint Portal Server 2001 to a document library on a Korean language version of SharePoint Portal Server 2003 (on a Korean version of Windows Server 2003).

Additional Considerations

• In a SharePoint Portal Server 2003 server farm, the operating system language versions must be identical. In addition, the language version of all the server farm SharePoint Portal Server installations must be identical (but they can be different from the operating system language version).
• Using the SharePoint Portal Server 2003 upgrade feature included with setup, the original six language versions of SharePoint Portal Server 2001 can only be upgraded to the same language version of SharePoint Portal Server 2003; for example, English to Korean upgrades are not supported.
• The names and values of custom properties used in document profiles remain unchanged. In most customer scenarios, the names and values of these document profile properties were already using the native language of the region.
• Site names, similarly, remain unchanged after migrating to SharePoint Portal Server 2003.
• Predefined, default properties in document profiles appear in the language version of the SharePoint Portal Server 2003 installation after migration is completed.
• The migration tool, Spout.exe, uses the same language version of the SharePoint Portal Server 2001 installation when exporting the content of the server.
• The setup program for the backward-compatible document library component of SharePoint Portal Server 2003 is only available in English. However, after this component is installed, the backward-compatible document library Web pages are displayed using the same language as that selected for the SharePoint Portal Server 2003 server installation.
• Custom digital dashboard Web Parts, whether localized or not, are not automatically moved to SharePoint Portal Server 2003.