TMGMT memory: adding memory capabilities to the translation management tool
Reñé Claramunt, Eduard
MetadataShow full item record
In the context of the CMS (Content Management System) on of the most used solutions is Drupal, a CMS which its best parts are its modularity, the big number of modules for it and the huge community mantaining Drupal and its modules. One of its modules is TMGMT (Translation Management Tool), it help
in the task of translating content in Drupal, as by default in Drupal you can just translate a text manually, writing for each contant a translation. TMGMT extend its capabilities letting us use other translators. Currently with TMGMT, if a content item changes in one field, it needs to be resubmitted as a whole to the translator. Without a translation memory, a translator is asked to perform the same translations again and again. If the user uses a non free translator this will mean that each time he will have to pay for it, leading to a over-cost to maintain a multilingual site. In MD Systems, Miro Dietiker wanted to solve that problem, but non of their clients wanted to pay for the development of this module, so they asked for funds to Acquia, this was meant to improve TMGMT Local module, to convert it to a CAT (Computer-Assisted Translation) tool, but to reach that goal, one of the steps was to add this translation memory to TMGMT. But Acquia refused to give funds to MD Systems to improve TMGMT claiming that TMGMT was good enough in features, and right now they have other priorities. But in MD Systems they still want to improve TMGMT. And I as part of the team in MD Systems and as I was working a lot in the port of TMGMT to Drupal 8, I wanted to see those goals reached, so I proposed to Miro Dietiker to build TMGMT Memory as my bachelor thesis, he liked the idea and agreed to give me support, so I dropped my initial thesis and started with it also with the support of my supervisor Marta Oliva.
The following license files are associated with this item: