TMGMT manages the translation process of a text source with the help of a translator. In the final version it will be able to use any given source, using any given translator, human or machine-based. Its plugin architecture allows for additional sources and translations services to be included at any time. For more information see here.

Sources

All Drupal text elements can be used as source for translation:

  • Nodes
  • Entities
  • Strings (Menu, Terms etc.)

A plugin architecture allows for the introduction of additional text sources (internal and external). Details see Sources Architecture

Translation Services

External translation services can be used for creating a foreign language version of the source text. Or it can be presented to a user for translation. A plugin architecture allows for the integration of additional services.

As of 11/2019, following service providers are available:

Note: (D7, D8) means that the module is available for D7 and for D8, but the one for D7 was not available in the final release or not covered by the security advisory on 20/11/2019. For an up to date list, please follow this link.

Included

  • Export and import via xliff and HTML
  • "Drupal User" Local Translator (Allows users to translate jobs)

Machine translation

  • Deepl (D7, D8)
  • Google Translate (D7, D8)
  • Microsoft Translator (D7, D8)

Translation Service Providers (translation by humans)

  • Acclaro (D7,D8)
  • Capita Translation and interpreting (D8)
  • Euroscript Global Content Management X-Connect (D7, D8)
  • Gengo (D7, D8)
  • GlobalDoc’s LangXpert (D8)
  • GlobalSight (D7, D8)
  • Lionbridge Translation Provider (D7, D8)
  • LiveWords (D7)
  • Memsource (D7, D8)
  • Nativy (D7)
  • One Hour Translation (D7, D8)
  • SDL BeGlobal (D7)
  • Smartling Global Fluency (D8)
  • Supertext (D7, D8)
  • Textmaster (D7, D8)
  • thebigword (D7, D8)
  • Translations.com GlobalLink Connect (D7, D8)
  • Wordbee (D7, D8)

Special purpose:

  • REST Translator (D7) - for developers

Additional translators in discussion. Proposals are welcome.

Translation Process

With tmgmt installed, the 'translate' tab of a node changes. You can choose
one or more languages to translate the node to and 'Request a translation' with
the corresponding button.

A translation job is created for each language chosen. It will run through the
following states:

unprocessed Translation requested in the 'translate' tab of a node.
Settings of the job (label set, translator chosen) defined.
The job was saved.
active The job is in the process of being translated, or needs a review. Depending on
the chosen translator, the actual translation happens auto-
matically or by a human being.
In all cases the job is returned to the job queue for review.
When the review is done, the status of the job item goes from
'needs review' to 'accepted'.
finished The job has been accepted and the translated node was created

A job deleted from the list is not visible any more. You can choose to purge
jobs automatically from the list after a defined time span. See tmgmt settings.