On this page
- Important note to translators
- How to become a language maintainer
- How to add a new language to Open Atrium
- How to bulk update translations
- See also
It is important to insure that translations are general and not site-specific. Please see here for more information.
To become a language maintainer, first check the downloads page to see if there is a current maintainer for your language. If there is, click their username and then click the Contact tab to send them a message. In your message, include which language you would like to help maintain as well as your username. If there is no current maintainer, send the message to us on translate.openatrium.com.
Because Open Atrium leverages the Drupal platform, we want to insure that any translations for Drupal itself are submitted through localize.drupal.org so that other Drupal users can benefit from the translations. So before we can add a new language to Open Atrium, it needs to be added to localize.drupal.org.
First, go to localize.drupal.org and browse languages there to see if your language is listed. If it is not, scroll to the bottom of the page and read the section titled How to get your group set up here?
Once your language is set up on localize.drupal.org, submit a request to us with the language you would like to add and your username. Each language needs a maintainer to administer the translation and manage the translation team for that language, so if that's not something you're interested in, you will need to find someone who is.
Once we receive your request, it may take some time before we are able to add the new language, but we will let you know as soon as the process is complete.
In addition to adding translations through translate.openatrium.com or by using your own site, language maintainers are able to upload bulk translations as well. This can be much quicker than using the web-based interfaces.
To get the latest version of your language file, visit your language page on translate.openatrium.com and select the Export tab. The page should look something like this:
The Project field lists a number of different groupings of translatable strings. The atrium package contains all strings, while the other packages contain subsets of the full package. Working with a subset can be useful if multiple maintainers are using this method to upload translations and you don't want to override each others' work.
Once you select a package, select the specific release you would like to translate for. Most likely this will be the latest version, which will be at the bottom of the Release select list:
For Type, leave it at the default Include both English originals and translations.
For Packaging, select All in one file.
For Verbosity, select Verbose files useful for desktop translation.
Then, click the Export button. It may take a few moments while the server compiles the file.
Once the file has downloaded, open it in a .po file editor such as Poedit.
When you are done editing the language file, save the updated version.
To import your language file back to the server, go to the Import tab in your language on translate.openatrium.com:
Browse to the file you just saved (1).
If you are compiling translations generated by a team, select Bulk Import for Atribute import to (2). Otherwise, leave your username selected.
If you would like others to help verify the translations you are updating, select Sore as suggestions needing approval, possibly discussion for Status (3). Otherwise, leave it at Store as approved translations.
Click the Import button.
- Use translate.openatrium.com to Contribute Translations
- Use Your Own Site to Contribute Translations