{"id":759,"date":"2014-06-04T17:29:45","date_gmt":"2014-06-04T16:29:45","guid":{"rendered":"http:\/\/wasaty.pl\/blog\/?p=759"},"modified":"2014-06-04T17:30:15","modified_gmt":"2014-06-04T16:30:15","slug":"759","status":"publish","type":"post","link":"http:\/\/wasaty.pl\/blog\/2014\/06\/04\/759\/","title":{"rendered":"memoQ 2014 – first impressions"},"content":{"rendered":"
Tweet<\/a><\/div>\n

\"new_memoQ\"New memoQ is coming and you\u2019d better grab it as soon as it arrives!<\/p>\n

Kilgray assumed a steady schedule of new major memoQ versions \u2013 once a year, somewhere during the summer. This time it\u2019s June, the version is 2014, and the list of changes and new features is really, really long. I have the privilege of using the \u201cpreview\u201d copy of memoQ 2014 and below I have summarized some of the new features and my experience of using it exclusively for the last two weeks.<\/p>\n

<\/p>\n

When I received access to the memoQ 2014, I\u2019ve also got a file with a short description of main changes\/new features which covers 26 points. Overall there are over seventy new features\/improvements in this version, and it\u2019s a huge list. I don\u2019t think there were ever so many new goodies included in a new memoQ release, and I\u2019m using the software since version 3.6. These changes are big and small and I must admit I\u2019m often finding these little ones very helpful. I\u2019ve already tweeted about some of them, but I\u2019ll try to mention them here too.<\/p>\n

So let\u2019s start with the biggest new feature:<\/p>\n

Project templates and automation<\/h3>\n

This is huge. Both for PMs and individual translators. Basic idea is that you can define a template for a project with particular settings and then create new projects in just three clicks (not including importing files for translation). Obviously it won\u2019t be useful for every kind of projects, but I think everyone does have some projects that can benefit from this kind of automation. In my case it\u2019s a broad category of MSDS-related translations (this includes translation of MSDS documents, chemical compound names and sentences and phrases related to REACH, ECHA and CLP). I can safely use single, end-client independent TM for them as well as fixed set of TBs and reference LiveDocs. Previously I had just one \u201cstanding\u201d project for MSDS jobs \u2013 I was adding new documents for translations, occasionally removing old ones, when the list became too crowded.<\/p>\n

\u00a0\"Template_1\"<\/a><\/p>\n

Now I\u2019ve defined a template: when creating a new project all I have to do is to import documents and enter the project name. I can use just one TM or memoQ can automatically add all TMs or other heavy resources with a defined set of metadata (e.g. domain and subject). After the files are imported to the project, they are automatically analyzed \u2013 you can define quite a lot of automatic actions, like pre-translation or copy source to target. Now, there is an interesting part: you can define separate working<\/b> and master<\/b> TMs. Master<\/b> TM will be used for pre-translation and reference while working<\/b> TM will be used to store confirmed translation units. To populate master TM with your current translation you need to use Confirm and update rows<\/b> command. My first thought was \u201cit does have its merits, but it\u2019s messy and a lot of work\u201d. But not necessarily \u2013 thanks to automation you can automatically populate master TM and delete working TM by executing new Wrap up<\/b> command. If you are performing a lot of verification and correction steps, it\u2019s an easy way of keeping your master TM clean. And if you don\u2019t, you can still use just one working\/master TM.<\/p>\n

\"Template_2\"<\/a><\/p>\n

At the moment there\u2019s just one quirk: memoQ will insist of adding language combination to your TM name, so in my case when I defined \u201cMSDS\u201d TM, in projects from template memoQ created new, empty \u201cMSDS-en-pl\u201d TM. In the end I\u2019ve cloned my TM calling it \u201cMSDS-en-pl\u201d and then it finally worked. (The template setting for TM is still \u201cMSDS\u201d, but memoQ actually uses \u201cMSDS-en-pl\u201d. It may be a quirk of preview software version and maybe it will be fixed before release.<\/i>)\u00a0 The interface of template editor could use some polish too, e.g. you can add additional TMs to a template by clicking on their names, but to add master TM you need to type in the name by hand.<\/p>\n

Nevertheless, templates seem to be very elastic and can accommodate different needs easily, so I\u2019ll definitely define several more templates for other types of projects soon (e.g. for SPCs). Oh, and \u201cwrapped up\u201d projects are displayed in green on the projects lists. Nice touch.<\/p>\n

Embedded objects<\/h3>\n

Excel embedded in Word or some similar combination. There are plenty of workarounds for this kind of files, usually involving renaming files, extracting, substituting \u2013 generally doable but messy. Not anymore. memoQ can now automatically extract embedded objects and present them after importing with proper native filter. So when you open a word file containing some Excel sheets, you can open all the files separately. And this also brings…<\/p>\n

Redesigned Translation tab<\/h3>\n

\u00a0\"Translations_1\"<\/a><\/p>\n

When you open the Translation panel you will notice some changes \u2013 previous grid with detailed information on file path, import\/access date etc. was replaced with much cleaner view with graphical representation of translation progress for files\/folders. But most importantly there are two options available here: Structure and Details. Press Structure to display files sorted by folders, with proper nesting. This view will also show you embedded objects mentioned earlier. And you can use Details button to display information on a particular files, including name of the filter used to import the document.<\/p>\n

\"Translations_3\"<\/a><\/p>\n

Although the colors used for graphical representation of the work status for any given file are not particularly appealing, the idea is great. And if you want to sort files in Translation pane using criteria different than default, just use Sort by<\/b> drop down. BTW, this version finally fixed long time \u201corder of files\u201d problem in views. Now when gluing files into view, they keep the order in which they are sorted in Translation pane. And another new feature for views: preview<\/b>. This obviously works only for simple \u201cglue together\u201d, but it\u2019s very nice nevertheless.<\/p>\n

New tag handling<\/h3>\n

The standard way of inserting tags in memoQ is to use of F8<\/b> and F9<\/b>, depending on tag type. Now there\u2019s a new way of inserting tags: Tag insertion mode<\/b> (F6<\/b>). When you press F6<\/b>, mouse pointer changes, showing miniature tag next to insertion point. In the tag insertion mode you can quickly insert (or remove) tags by just clicking with mouse. I appreciated this in one of the jobs I did recently, where I had plenty of high-percentage matches from TM, but the matches had none of the multiple source tags. Using tag insertion mode I was able to insert missing tags quickly and effortlessly. What\u2019s more, there is a new Arrange tags<\/b> function. If you have messed up your tags, just press Alt-F6<\/b> and memoQ will automatically arrange target tags in the order they appear in source segment. This can be very handy. I just wish the feature would be available in Resolve errors and warnings<\/b> dialog \u2013 it would make life even better.<\/p>\n

Term bases improvements<\/h3>\n

There\u2019s a whole batch of new features in this category. We have new TaaS service<\/a> integration \u2013 cloud terminology extraction and management service. When it comes to term extraction TaaS can do more than memoQ. You can create term collections in the service and use them directly in memoQ, almost like local term bases.<\/p>\n

Finally there is a duplicate detection and removal function (available for TMs too). And it automatically detects an attempt to add duplicate term \u2013 this is extremely useful especially for an online multilingual TBs, where it was very easy to create multiple entries for a single term.<\/p>\n

\u00a0\"TB_duplicate\"<\/a><\/p>\n

Term bases can be sub-language sensitive \u2013 it means no more EN-GB hits for EN-US project, but it\u2019s an optional, per-project setting.<\/p>\n

Last terminology improvement concerns Trados Studio packages \u2013 now it is possible to import term base content from package too (if there is one in the package).<\/p>\n

Various bits and pieces<\/p>\n

There are some additional new features and improvements:<\/p>\n