• What exactly is the Translation Management Tool?
    • Started at a Sprint a year ago here in Zurich, initiated and supported by Miro Dietiker, among others.
      Does not introduce new translation functionality but builds on top of the existing content and entity translation modules.
      The focus is on the management of the translation process. Instead manually creating a translation by copy and pasting translations, it allows to create a job that can be sent to a local or external translation service.
      Various translation services are supported, local users, exporting XLIFF files, machine translation and translation agencies like Gengo, Supertext and One Hour Translation.
      The complete workflow of creating a translation is kept under control at any point, including quality control, review processes and saving the translation back to Drupal.
      It provides various management views that give an overview over the translation status of your site and pending translation jobs.
  • How does this integrate, or play nicely with i18n?
    • It currently accepts nodes and entities as input. Integration with interface translation and so called i18n objects (menus, terms, views) is initiated but not yet complete. (Help is welcome!)
  • What is the current state of development?
    • We are preparing the first beta release, to be released within the next weeks. The focus of this release is node and entity translation, improved user interfaces and the new local translator.
      The development version can be downloaded on the project page and we have a lot of automated tests to make sure that this version is as stable as possible.
      Apart from the core project, there is a translation server distribution coming. It is based on the google summer of code project by Sebastian Siemssen (fubhy). We will release a first version of that distribution together with the beta release.

Use Cases

At any given time, you can take a single node, send it to a translation service like Gengo, review translation and save it back in a single user interface.
Use the provided rules integration to automatically create a machine translation for all languages that your site supports when a news article is created.
Request a translation of all pages from your local translation team, which can use the local translator that provides a separate User interface on the same site.
Do the same for several sites, using a centralized translation server so that your translators only need to access a single site.
Or you can use our directory listing to find the best external translator for your content.

Questions from Twitter