Last updated August 19, 2013. Created by AllanTheDream on August 15, 2013.
Log in to edit this page.

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

  1. Download the translation files of the profile in your preferred 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. Run the installer
  4. Select the language at the Select language page of the installer, the profile will be installed in your preferred language.

Translating OpenAidMap modules whose translations are not hosted on the Localize server
Translating a module's strings involves two files, the .pot file and the .po file. The .pot file is the template file with all the strings from the module not translated, and the .po file is the .pot file translated to a particular language (to translate the strings of a module to a particular language one uses the template file).
Translation files of a module are kept in the translations directory of the module.
So to translate a module's strings to any particular language, one needs a .pot file (the template file) and an editor, preferrably a Gettext editor, and by importing the .pot file into the editor one translates the .pot file hence coming up with the .po file in a given language e.g de.po for the German translations, es.po for the Spanish, etc
Using the .pot file the strings of the module (or any other project) can be translated to multiple languages, one only needs an editor and most preferrably a gettext editor.

Looking for support? Visit the Drupal.org forums, or join #drupal-support in IRC.