Multilingual

Automatically rewrites output HTML media tags (img, object, embed) to use translated versions of media, if files are present on disk.

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

TODO

This a is a module developed in response to the thread here: http://drupal.org/node/130389

In summary, Nodewords works wonderfully for nodes in a multilingual setting because each translation of content is a node and has it's own meta information. The problem is that for pages like the homepage, 403 and 404 pages, nodewords only provides one default set of meta information fields. So if you were to set the meta information in English, viewing your non-node based homepage in Spanish would still generate the english meta information.

This module duplicates the fields for languages enabled on your site. It saves that information in a separate DB table called nodewords_translate, and when viewing a translated non-node based page, it will substitute your translated meta information.

Requirements
Branch 6.x-1.x gives support for Nodewords 6.x-1.11
Branch 6.x-2.x gives support for Nodewords 6.x-1.13
Further development
Thanks to jyee granted me, plopesc, as comaintainer. Now I'm working on the following developments:

• Support for the latest nodewords release
• Improve features, as support for custom pages
• Include testing support

This module handles contexts for locale. It requires the custom-locale core patch, which is bundled (for Drupal 6.20) with this module.

Under /admin/settings/language/contexts the available and default contexts are managed.

"Available contexts" are the contexts available to the system.
"Default contexts" are the default contexts for the site, FILO fallback.

The translation integrates into Drupals core Locale module.

Allows the administrator to specify a theme to use per language.