Multilingual

This is a small utility module that extends the language negotiations to use multiple domains per language.

Use cases:

• You have a bilingual website with the different domains mapping to the same language:
  • English (default): example.com, example.co.uk
  • German: example.de, example.at
  • Spanish: example.es, example.ar, example.mx
• You want to use the same language negotiation settings for development, staging and live:
  • English: example.com, dev.example.com, staging.example.com
  • German: example.de, dev.example.de, staging.example.de
  • Spanish: example.es, dev.example.es, staging.example.es

Expose Drupal translation activity in meaningful chunks and visualize it.

Lingotek Translation is a community-maintained module that is primarily sponsored by Lingotek and built on Drupal's standard multilingual modules (locale, content translation, entity translation, internationalization, etc). The module helps Drupal administrators, agencies, and web marketers to:

1. Get a Drupal site multilingual-ready within minutes (instead of days)
2. Translate Drupal content using machine translation and/or human translators with access to your site
3. Lingotek offers extensive professional translation and localization services. Lingotek's Language Services team includes professional, in-country linguists, localization project managers, and localization engineers - all of whom ensure the highest-quality of translations. Should you have existing translators or vendors, it is possible to continue working with them on the Lingotek TMS.
4. Automate the ongoing synchronization of multilingual content via customizable translation workflows
5. Ability to do in-context review of content

Lingotek for Drupal 8

The module supports translation of any content and configuration, including:

• Content entities - nodes, comments, messages, taxonomy terms and even paragraphs (including nested ones)
• Configuration entities - fields, blocks, taxonomy vocabularies, views, fields, etc
• Configuration items - site name, system emails, etc

If a contributed module is translatable using Drupal 8 core features, there is a big chance that it works already with Lingotek.
As a result of our experiences with clients and our automated testing, we can ensure that the following contributed modules are supported:

• Pathauto
• Paragraphs
• Metatags
• Webform
• Group
• and many more!

Lingotek for Drupal 7

The module supports translation of:

• Entity types - nodes, comments, messages, paragraphs, beans, groups, commerce products, fieldable panels panes, taxonomy terms with custom fields, and even field collections (including nested ones)
• Taxonomy terms - your choice of an Entity Translation approach for terms with custom fields or the i18n string approach for translation of name and description fields only
• Configuration items - field labels, blocks, taxonomy vocabularies and terms, menus, views, webforms, etc.
• Properties - titles, path aliases, and metatags
• Built-in interface strings

In addition, translations for nodes can be stored using either the field translation (recommended) or node translation methods.

This is a proof of concept for dynamic data translation.

What works:
- Query mangling with hook_query_translatable_alter(), only tested with roles on admin/permissions/roles
- Listing oft tables/fields with the translatable tag, creation of translation tables for each separately

There is no translation UI yet.

This module simply modify the theme registry & locale settings to force Theme to be LTR to be set when uid=1 [admin]

Use Google Translation API to add a "default translation" for non-translated strings.

What this module does is translate on each cron call a number of those strings, allowing later to check and to correct them

This modules is an add-on to Nodequeue, it allows you to create a smartqueue that provides a subqueue per language.

This allows you to create a single nodequeue, and yet have different results in your queue based on the sites language. Smartqueue language will automatically create a subqueue for each configured language.

A very simple module which would allow you to show all/any comments attached to all node translations. Just a great way to communicate in truly multi-lingual environments.

For example I have node in English and Spanish. Drupal natural way would be to show comments for en/es translation separately (attached to en/es content). But i18n_comments will aggregate all English and Spanish comments for any translations. It doesn't matter if user will leave a comment to any node translation.

This module provides a copy/paste based integration with Google Translation Tools http://translate.google.com/translate_tools for your Drupal site.

Security was not addressed in this module and there is a hole, since you're pasting a script in that gets injected into the head of the document. Seems fine otherwise though. Fun little project for an afternoon, but I've found there are too many similar projects for this functionality and decided not to keep working on it.

i18n Localized Variables extends Internationalization module to let Drupal utilize localized variables for each enabled language without modifying sites/default/settings.php.