The Contact translation module, part of the Internationalization (i18n) package, helps with the multilingual configuration of the site contact forms.

Dependency

The Contact translation module has a dependency on the core Contact module.

This is a list of additional contributed Drupal 7 modules that extend Drupal's multilingual features:

Administration

• Language Assignment: Lets you set the language of multiple nodes or users at a time.
• Translation Overview: Provides a comprehensive view of your content translation status.
• Translation table: UI for quick translation of taxonomies and menus.
• Taxonomy CSV import/export: A UI / drush tool useful for creating multilingual taxonomies.
• Translation Management Tool: Provides a tool set for translating content from different sources. The translation can be done by people or translation services of all kinds. It builds on and uses existing language tools and data structures in Drupal and can be used in automated workflow scenarios.

User Interface

• Language Icons: Adds icons to language links for nodes and blocks.
• Language Switcher Dropdown: Provides a new block with the language switcher as a drop down field.

This is a list of other contributed modules that extend i18n features:

• Internationalization Helper, Provides more options for synchronizing CCK fields.
• i18n page views, Provides a views display for which you can select a path for each language.
• i18n media, Automatically rewrites output HTML media tags (img, object, embed) to use translated versions of media, if files are present on disk.
• Language Assignment, lets you set the language of multiple nodes or users at a time.
• Menu translation (Node), allows a single node menu item to point to different node translations belonging to the same translation set depending on the current language.
• Language Switcher Dropdown, provides a new block with the language switcher as a drop down field.
• Active Translation, shows original language version of content in listings, if content has no translation yet.
• tContact, make the site-wide contact form fully translatable.

Inserting the following variables into your settings.php will make them available to Drupal's translation system:


/* User_relationships */
'user_relationship_mailer_request_subject',
'user_relationship_mailer_request_message',
'user_relationship_mailer_cancel_subject',
'user_relationship_mailer_cancel_message',
'user_relationship_mailer_approve_subject',
'user_relationship_mailer_approve_message',
'user_relationship_mailer_disapprove_subject',
'user_relationship_mailer_disapprove_message',
'user_relationship_mailer_remove_subject',
'user_relationship_mailer_remove_message',
'user_relationship_mailer_pre_approved_subject',
'user_relationship_mailer_pre_approved_message',
'user_relationships_ui_msg_submitted',
'user_relationships_ui_msg_accepted',
'user_relationships_ui_msg_disapproved',
'user_relationships_ui_msg_cancel',
'user_relationships_ui_msg_default',
'user_relationships_ui_msg_removed',
'user_relationships_ui_msg_pending',
'user_relationships_ui_msg_pre_approved',
'user_relationships_ui_msg_too_many_relationships',
'user_relationships_ui_msg_existing_request',
'user_relationships_ui_msg_existing_relationship',
'user_relationships_ui_msg_not_accepting_requests',
'user_relationships_ui_msg_self_request',
'user_relationships_ui_msg_non_existant_user',
'user_relationships_ui_msg_non_existant_type',

The Translation redirect module, part of the Internationalization (i18n) package, improves search engine optimization (SEO) for multilingual websites. By default, multilingual pages can be accessed via different paths by changing the path prefix or domain. Search engines tend to penalize displaying the same content at more than one URL, so it's important to redirect to a single instance of the page.

The Translation redirect module redirects anonymous users (including web crawlers) to the translation of the page in the requested language, if it exists, using a 301 redirect code. For example, if the request is for /de/node/23 and node/23 corresponds to an English page, the user will be redirected to the German translation of the English node if it exists. If the translation does not exist, then the source node content is displayed.

Note that, by design, translation redirection does not work for the homepage or for authenticated users.

Design and Dependencies

The Block languages module, part of the Internationalization (i18n) package, allows you to configure for which languages each block is visible. The settings for visibility per language are provided under Visibility Settings via the Languages tab when configuring a block.

Figure 1

The Languages tab also provides a setting for whether the block is translatable. For custom blocks, the block title and block content will be translatable. For blocks defined by modules, only the block title will be translatable. If Make this block translatable is selected, a Translate tab will appear for that block. This tab provides a UI for adding translations of the block in each available language.

Don't forget to allow your used string format to be translated on admin/config/regional/i18n/strings or you are going to have a error message like The string blocks:block:1:body for textgroup blocks is not allowed for translation because of its text format.

More infos http://hojtsy.hu/blog/2011-apr-03/drupal-7039s-new-multilingual-systems-...

Conflicts with Context