i18n localization procedure for OA

This documentation is about using Open Atrium in another language than English, not about using it on a multi-language site. These are the steps I follow for a fresh installation:

Basic language installation

1. Enable core Locale module
2. Enable the language you want to use (admin/config/regional/language/add)
3. Switch to the new language (admin/config/regional/language) by setting it to the default. Move it above English. Uncheck English.
4. Install and enable the Localization Update module.
5. Go to the Translation update administration page at admin/config/regional/translate/update
6. Update all language files.
7. Clear cache

You now have all existing translations from localize.drupal.org for the language of your choice. You will find many places though where translation is lacking, both on the administration pages and the end user interface. Focus on the end user interface by creating a normal user account and log in as a regular user to find spots that are not translated, or not translated to your liking. You should repeat this for different roles on your site.

Further customisation

1. Install and enable the Localization Client module.
2. Create a shortcut in the admin menu for admin/config/regional/translate/translate.
3. Use both tools to further translate your site. When using the new 2.60 Atrium theme you will find that the "translate" button in de lower right corner is overlapped by the new edit buttons.
4. To translate Messages first go to admin/config/system/message/text-copy and copy the text fields from "Language none" to your new language. Then translate each message at admin/structure/messages.

Known difficulties, items to discuss

• Open Atrium uses specific terms like 'Space' and 'Section' that can have a different meaning depending on your usecase.
• Updating the language files: you should be careful with language updates once you have customized your site. You need to make sure your customizations are not overwritten. So when you go to admin/config/regional/translate/update you should choose the update mode carefully.
• Several spots in the Open Atrium interface need custom translation: for instance the node/add buttons (admin/structure/command-buttons/manage/node-add), Space and Section names (found on the taxonomy pages admin/structure/taxonomy, the names of the node types that need to be translated at admin/structure/types, etc