Last updated November 5, 2012. Created by cgalli on February 19, 2012.
Edited by frederickjh, ethanethan. Log in to edit this page.
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 (TODO: Link) allows for additional sources and translations services to be included at any time.
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
Status 19. Feb. 12: Nodes/Content can be translated. Entities and string working, but user interface not yet implemented
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.
The following services are being worked on at the moment:
- Local users. Present a user with a two panneled page for immediate translation. Not yet functional
- Microsoft Translate (machine). Working as well as a machine can translate. Its a good starting point, but the text must be adjusted for better understanding
- Nativy (human). Initial implementation done but currently broken. The integration is also not satisfying yet.
- MyGengo (human). Initial implementation done, ready for testing.
- Supertext (human). Development has started, not working yet.
- File export and import via xliff and html is functional.
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.