The first experiment used MemoQ as a CAT tool by using the text attached in the appendix. The approach considered MemoQ as a multilingual text archive that contains multilingual texts (parsed, segmented, aligned, and classified). The tool is taken to have the ability to store and retrieve aligned multilingual segments of the same test against different search conditions that were made.
The second experiment used Trado as a CAT tool by using the source text as attached in the appendix. The pre-segmented Trados file was put in MSWord format
The source and target of the translation unit were separated by the match statistics which Trados generated (however, the RTF contained the language definitions for the file). The figure below indicates the Trados RTF file.
From the two translated texts (see appendix 2 and 3 for Trado and MemoQ respectively) we have noted that when the same text is translated from Trados and MemoQ, Trados offers a platform for auto-completion feature which in turn, provides the process of translation with a unique dictionary of aligned phrase that can be extracted from an existing as well as adequately large translation memory (TM). The phrases, on the other hand, are suggested to the users as they are typing. The phrase suggestions are what Arenas (2014) terms as ‘prefix’ (p. 47). This advantage indicates that in the past few years, TM developers have been focusing on improving Trado by integrating sub-segment matching termed by Arenas (2014) as ‘concordance’ as well as predictive sub-segment matching which is advanced compared with MemoQ. This approach, in turn, shows that Trado is advancing TM leverage more than what MemoQ is offering. As the process of translation was taking place, the auto-suggest and concordance offered by Trado were useful for context and terminology checking but preferring to have the option off was better as it distracted.
Differently, the alignment feature provided in MemoQ has been integrated into the software’s LiveDocs component, which offers a unique element when working with MemoQ. Accordingly, this feature is a separate resource database where one can put into the system both bilingual and monolingual files that can be used for automatic lookup and processes of insertion. To ensure that the process of translation is consistent, MemoQ, unlike Trado, provides a platform where one can maintain TMs periodically. This is not to mention that its platform is further equipped with an interface where one can correct, edit, delete or add segments. Again, while the two tools offer acceptable levels of consistency, MemoQ has increased levels of consistency because it offers the opportunity for users to recycle existing translations. Just like Zaretskaya (2016) noted, a tool with the ability to recycle existing translation improves the quality of translation, we noted that the best out of MemoQ would be possible when its database is maintained. Instances of perfect matching or exact matching were well elaborated more in MemoQ compared to Trado. While translating part or section of the text that was already translated before, MemoQ was able to suggest the old sentence or segment within its database. The difference between the two tools was that when the translation was using MemoQ the exact match could occur when the term from the new second language was identical to the old term, provided it was found in the MemoQ TM database. The two tools differ in terms of their active terminology recognition. Generally, the two tools provide an opportunity where the translator can take advantage of different terminology databases which they create. According to Weitz (2017), this means that translators are allowed to connect the TM to the tools ‘termbase.’ However, MemoQ provides users with the ability to manage multilingual glossaries. The tool is designed in a way that it can maintain multilingual glossaries in what it is termed as ‘termbases’ the tool has connected TM.
Read More