Translating the OpenAidMap profile can take two routes, either at installation or after installation of the profile;

Translating OpenAidMap after installation

1. Download the translation files of the profile in the given language from the http://localize.drupal.org server.
2. Place the translation file in the translations directory of the profile i.e profiles/openaidmap/translations
3. Go to the Languages page (/admin/config/regional/language) under the Regional and languages configuration page.
4. On the Languages page, click the "Add language" button, choose your preferred language from the drop-down list of the supported languages and add the language by clicking the "Add language" button.
5. Translation files of the profile and modules will be imported into the database.
6. After the translation files of your preferred language have been imported, you can set the particular language as the default by checking the "Default" radio button next to the language and then click the "Save configuration" button.

Installing OpenAidMap in your preferred language

This is a summary of the process of how to setup a multilingual site with domain access. Please feel free to edit any parts which are incorrect or that may confuse users. Content is based on how we made our sites work and on this tutorial by Jose Reyero:
http://reyero.net/drupal/internationalization_domain_access_multilingual...

If you have installed Domain Access and all seems to work fine, but then you want some domains (or subdomains) to be in different languages, for example:
- maindomain.com (english)
- sub.domain.com (french)
- domain2.net (spanish)
- sub.domain2.net (spanish)
- domain3.com (english)
- domain4.org (german), etc.

The following is assuming you correctly setup your affiliate domains and/or subdomains in your settings.php file.

Change the default language
1. Enable the correct modules (Domain Access, Domain Variable, Domain Locale, Internationalization & Variable). See links to these modules at the end of this page.

2. Enable the languages you will be using here: admin/config/regional/language

3. Enable URL detection method here (must be Path prefix): admin/config/regional/language/configure

This documentation page is based on an extensive comment by j2b. Needs rewording and style review. Will need updating once the commerce patch in #1495570: Update Entity translation integration is committed.

Configuration examples

• Translate taxonomy terms in title and breadcrumb
• Show taxonomy term language
• Multilingual taxonomy term list

About multilingual fields

Entity fields natively implement multilingual support. The language associated with a field depends on a number of factors including if translation is enabled and the chosen translation method (e.g. for node entities, either node translation or field translation).

Before looking at the specific field language support, it is important to know the different possible entity configurations. For node entities, content types can be configured as follows:

• Locale module is disabled
  • No language assignment
  • No translation
• Locale module enabled
  • Language assignment
  • No translation
• Locale and Content translation modules enabled
  • Language assignment
  • Translation via node translation method (multiple nodes)
• Locale and Entity translation modules enabled
  • Language assignment
  • Translation via field translation method (one node)