Multilingual

Provides one-way string transliteration (romanization) and cleans file names during upload by replacing unwanted characters.

Generally spoken, it takes Unicode text and tries to represent it in US-ASCII characters (universally displayable, unaccented characters) by attempting to transliterate the pronunciation expressed by the text in some other writing system to Roman letters.

Connexion Corporate Communications presents the Automated Web Translation Workflow (AWTW) module which allows you to export and import from the Drupal administration all – or part of – your website content. With the AWTW module translating your web content has now become child’s play.

The content is exported into an XML format that is compatible with most Computer Assisted Translation tools (such as DéjàVu, SDL/Trados, Wordfast, etc), allowing your human translators to use their own specialized work environment. After translation, you can import the translated content via the Drupal interface, with just a few mouse clicks. The module automatically creates your new language pages in the source layout and links them to the original items.

If you’re interested in this module, make sure to check out the demonstration video at: http://www.connexion.eu/awtw

Taxonomy is one of the coolest features of Drupal, allowing the creation of information which is organized and structured. Taxonomy can be key for your visitors to find what they are looking for.

Creating a high-quality and complex taxonomy is a lot of work. Folksonomies and tagging makes for a more accessible implementation, but some of the value of having hierarchical, structured taxonomy for disambiguation is lost. The machine tags module is meant to fill a void between people-friendly tagging and machine-friendly hierarchy.

Translatable module is a different approach on internationalization and localization. It uses the merits of the Forms API to control the behavior of input elements when creating translations of existing contents.

Designed for multi-language sites, Language Sections provides a way of storing content sections for different languages in a single text area.

Applications include

• A simple multi-language site front-page.
• Views module header, footer and "empty" text sections, to make them "language aware".
• Translated Custom Tokens.
• Language-specific custom 404 pages etc.
• Text sections provided by other modules which do not offer multi-language capability.
• An easy to manage alternative to the Content translation module in some situations, typically on small sites.

The Google Language API family has been deprecated, unfortunately making this module obsolete. Read Google's announcement here.

--

This module makes comments on your site translatable. It adds buttons to each comment for various languages. Clicking a language will translate the comment using the Google AJAX Language API.

The Language API is loaded externally from Google. More information about the API can be found here:

The Translation Overview page provides a table listing the site's nodes and showing what's been translated into each language. It also lets you assign priorities for translating nodes into the various languages.

For translations of taxonomy terms and menu items check out the Translation table module.

The Active Translation module is designed for internationalized sites where translated versions of content need to be displayed when available but if they're not the original, untranslated content should be displayed. If several regional versions of a language are available these will be used as substitutions.

Oct 12th, 2008: I'm looking for co-maintainer for this module so if you're using this module and have some development experience either open an issue or contact me. I personally have no plans to port this to Drupal 7 so if you're interested please consider taking over the module.

This module implements various utilities for sites that can have an interface language different than that of the content language.

In particular :

• Alter all links to translations such that they do not change the interface language when changing the content language
• Provides an interface language switcher block. This only switches the language of the interface (when i18n is installed, the local language switcher block changes both interface and content language).

This module also backports the following fix http://drupal.org/node/258785 from Drupal 7 to Drupal 6 : it ensures that content types without a language are set to 'Language Neutral' rather than the default language.

Description

Select translation implements a Views filter to select which translation of a node should be displayed in a list of nodes.

Several modes are available to select a translation:

• Use the current interface language; if not available use the original node language.
• Use the current interface language; if not available use the default site language; if not available use the original node language.
• Specify a list of languages, and use the most appropriate language.
  
  Some special values are recognized in the languages list:
  • "current" will be replaced with the current interface language;
  • "default" will be replaced with the default site language;
  • "original" will be replaced with the original node language.