When you’re done, click Save configuration at the end of the page. Drupal may request that you allow auto-activation of other language module, which these module require.

Set up ICanLocalize Translator

These settings will determine which translation languages will be availalbe via the ICanLocalize Translator module. Once you complete this setup you'll be able to use the Translation dashboard to send new and updated contents for translation by ICanLocalize.

Setting up translation languages

You need to define the target and source languages for translation. Select each language you want to translate from and then, the languages to translate to.

Before you add translation languages, you may need to add the languages to your Drupal site.

Translation pickup setting

You can choose how your Drupal site is notified of completed translations. There are two options:

• XML-RPC notifications - the site will be notified when new translations are ready
• Translation polling - the site will periodically check for completed translations using a cron-job

Choosing XML-RPC notification will make translations available as soon as they are ready. To use this option, your site must be accessible from the Internet. If your network configuration allows other servers to contact your site, this is the prefered pickup method.

If your site is behind a firewall or inside a closed network environment (such as a local Intranet), you should choose the translation polling option. This option will work for any Drupal install, regardless of network configuration, but translations will only update when your cron job runs.

ICanLocalize Account

This page will create an account for you in ICanLocalize. This account will be used to communicate with translators and pay for translation work. By default, a new account will be created. You can also use an existing account if you already have one.

Account setup requires an email and full name. This is only used to communicate privately with you and is not displayed anywhere.

There's no need for you to manually send and collect translations. This module does it automatically.

Translating contents automatically or manually

Next is the ICanLocalize Content setup. You can set here the method you want to post translation requests. You can choose to post only manually by the ICanLocalize Translation Dashboard, request options while editing a node or automatically send each and every node to translation on all available languages.

If you choose to prompt for each page, you’ll see the translation controls when creating or editing contents.

If you’ve chosen Manual translation you’ll need to manually send documents to translation from the Translation Dashboard.

You also can determine how to handle translations when the original contents are deleted.

Language and translation options per content type

Click on the content type you want to to enable translation for and then click on Edit.

Expand Workflow setting to select the language options. There, enable language selection and translation for each content type you want to translate.

In the Multilingual support section, in order to enable translation, you should select the last option (Enabled, with translation). This way, Drupal will display the content language selector and translation controls when you enter new contents.

Selecting which fields will be translated

You can choose which fields and node types are translated.

Expand the Content Translation group. Here you can see all the fields available for translation. Select the ones you’d like to translate.

Once all required content types have been set up, translation can begin. If you’ve chosen Automatic Translation in the configuration screen, you don’t have to do anything, just post any content and it will be automatically sent for translation.

Taxonomy translation and i18n module

To translate Taxonomy terms you will need the i18n module and to enable the “Taxonomy translation” module (go to the module administration and look under the Multilanguage section).

Then go to Administer > Content management > Taxonomy and edit each vocabulary you plan to translate terms from. On the Multilingual options section two options are supported by ICanLocalize Translator:

• Localize terms
• Per language terms

* Set language for vocabulary isn’t supported due to a limitation in the i18n module.

When you’re done setting up the vocabulary, review the Content type settings for each relevant content type and select those vocabularies you wish to translate terms from, under the Content Translation section.

Once these settings have been applied, document translation will also include Taxonomy terms.

CCK integration

The ICanLocalize Translator module supports CCK fields on your content types. Not all widget types are adequate for translation. You can only translate the following field types:

• Text (textfield and textarea as well)
• Option (select, buttons and onoff types)

To translate these CCK fields, you need to enable them in Administer > Content Management > Content types under the Content Translation section for each relevant type.

Sending contents for translation

When you add new contents or edit existing contents, you’ll see a new translation section, created by the ICanLocalize Translator module. This section lets you control when translation is sent and which languages to translate to.

When adding new contents, you can choose whether or not to send to translation. When still editing, it’s better to hold off the translation (as human translators will start working on the translation as soon as you send it).

Translation Dashboard

The ICanLocalize Translation Dashboard will let you select the documents that need to be translation.

Select the contents you wish to translate. From the action selector select the language you wish to translate and press Update.

The translation dashboard lets you track the translation status, per node.