It may appear to you that analysing a large amount of files is our pet peeve, this being the second post about such an oddity. Anyone in the language industry is lucky enough to be exposed to an unhealthy dose of files, and we are happy to report having not only cooked up a remedy when it comes to Trados, but memoQ as well.
Five years after writing the original MutliAnalyze application, the need for an automatized analysis tool surfaced once again. memoQ has had a built-in feature for some time now to analyze all files in all projects, but exporting the results is still an unsupported, yet vital option, rendering this feature almost useless. To avoid the looming menace of unnecessary manual work that we have encountered before in the case of Trados, we took a jump start and recreated MultiAnalyze, this time, to be used with memoQ. The concept behind the new tool was exactly the same as for MultiAnalyze, which you can read more about in our previous post. The devil lay in the API, which differs substantially between Trados and memoQ.
memoQ WS API is based on SOAP API, and as such, seamlessly integrates with .NET and C#. This is a huge positive boon from a flexibility and compliance standpoint, and ensures that the same code can be applied to other uses as well. After C# 2.0, it was very refreshing to use version 4.0 for memoQMultiAnalyze, as the var keyword and the new dynamic features are considerable benefits for programmers. It was also a good opportunity to refactor some of the code from the old MultiAnalyze project and to store the application’s settings using .NET’s built-in feature instead of relying on the Windows registry.
The tool is designed to be user friendly. The user interface replicates memoQ’s familiar statistics dialog incorporating most of the options, enhancing usability. In addition, the application supports multiple memoQ servers (multiple SOAP endpoints), which is another comfortability feature for users who frequently use more than one connection.