Bamboo products can be configured to display product menus, user interface text, and settings in your local language. You can also customize the default text provided with the product. To change the language or text a product displays, perform the steps described in this article. Click a link below for detailed information about each step.
Note: This article applies to the specific products listed above. For instructions to customize text for other Bamboo products, see KB.12791 - How to localize Bamboo Web Parts. To customize text in Project Management Central, see KB.12764 - How to localize PM Central R3.0 for your language.
Customizing Language Files
About the Language Files
Text displayed in this Bamboo product may be included in one or both of the following locations:
- Provisioning Resources
\Program Files\Common Files\Microsoft Shared\Web Server Extensions\[12 or 14]\Resources\Bamboo.[Product].resx
This file includes text used in site features, site definitions, list definitions, and other provisioning resource elements. Changes apply to new product instances only.
- Application/Runtime Resources
\Program Files\Common Files\Microsoft Shared\Web Server Extensions\[12 or 14]\CONFIG\Resources\Bamboo.[Product].resx
This file includes text used in application pages, custom site menu actions, navigation elements, and other runtime resources. Changes apply to new and existing product instances.
In each location, there may be multiple, identical versions of Bamboo.[Product].resx provided for English (en-US), German (de-DE), French (fr-FR), and Spanish (es-ES). All files are in English until you translate them to your language. If your site is configured to use a language that does not have a corresponding Bamboo product .resx file, copy an existing file and rename it to include the culture name for that language pack. For example, create a file for Italian by saving the default file as Bamboo.[Product].it-IT.resx. Make your changes to this new file. If your site is configured to use a specific language but you do not have a culture-specific file, the product will use the default Bamboo.[Product].resx file instead.
If you customize one of the default resource files provided with the product, your changes will be overwritten when you upgrade. To avoid losing customizations, copy the customized file to a different location (not the same folder) before upgrading. After the upgrade is finished, compare the new file with your customized file to incorporate any new entries. Then copy the merged file to the Resources folder. Culture-specific files created for languages that are not provided with the product will not be overwritten during an upgrade, but you still need to incorporate new resource entries.
Editing Text in Resource Files
Stop! Before making any changes, back up your original file to a different folder.
To change text in a resource file, open it in a text editor and locate the text you want to change. Edit the text between the <value></value> tags. Do not modify the data tag. If you want to remove text completely, delete only the text; do not delete the <data> or <value> entries from the file, or the server will display an error message. In the example below, the text you can modify is highlighted in gray.
When you are finished with your changes, save the file and copy it to the appropriate Resources folder on all Web front-end servers in your SharePoint farm. Follow the instructions below to make your changes take effect.
Applying Language File Updates
Applying Changes to Provisioning Resource Files
If you modified the provisioning resources file, apply your changes by restarting Web services with the following command on all Web front-end servers. Reminder: changes to provisioning resources affect new instances of the Bamboo product only; existing instances of the product are not updated.
Applying Changes to Application/Runtime Resource Files
If you modified the application/runtime resources file, apply your changes by executing the following command all Web front-end servers. This command copies the updated resource file to the \App_GlobalResources folder of each Web application. Changes apply to existing product instances and any new instances you create.
> stsadm -o CopyAppBinContent