ICanLocalize Translator - offloading Drupal translations

My name is Amir Helzer and I'm responsible for ICanLocalize Translator - a new module that automates the translation process for Drupal (6) sites.

It complements i18n module by allowing to send new or updated contents to translation storing the translation back in the Drupal system.

Translation is provided by a team of professional translators. This module is intended for people who need translation for their Drupal sites and don't want to do the translation themselves.

Highlights

• Maintains the HTML structure - translators use a WYSIWYG editor which only lets them edit the text. The HTML, including formatting, embedded objects, etc. is kept the same.
• Auto adjusts links to other translated pages - if the translated page is linking to other pages that are translated too, links would update to the corresponding translation.
• Centralized management - translations are controlled from a centralized place, allowing to select nodes in a specific language that require translation. Then, all nodes can be sent for translation at once.
• Supports taxonomy translation. Nodes that are a part of a menu will be translated with the menu item text.
• CCK translation.

Our goal with this module is to allow people to run a multilingual Drupal site with minimal translation related overhead. Translation can happen on full auto-pilot without having to worry about site integrity in each language.

Where we are now?

We've released the 3rd Beta. Our demo site, Drupal Translation uses this module. It's available in English, Spanish and German.

The core functionality is working fine. In the next beta release, we're going to significantly simplify the module setup. Then, we're ready for a first public release.

We're looking for people who'd like to try it out and give us feedback. We'd love to hear your opinion about the concept and our implementation. You can contact me directly at amir(dot)helzer(at)icanlocalize.com.