Some new features in memoQ 6.2

I am proud to say that we are soon going to release the first beta version of memoQ 6.2, and by soon I mean tomorrow.
With memoQ 6, we already started focusing on some details that make the life of translators and project managers easier, and memoQ 6.2 follows this tradition.

I don't know if you remember memoQ 4.2. It was also a rounding-up release, adding some significant functionality that, on the other hand, did not turn the architecture of memoQ upside down. memoQ 4 introduced the concept of resources and multilingual projects, and that was similarly a huge release like memoQ 6. New filters, convenience features, changes that only affect the translator pro edition are considered to be relatively error-free. And these are the things where memoQ 6.2 is bringing improvements.

In this post I don't want to talk about the two large features, those can wait, but rather the smaller things. So let's see what you're able to do that you weren't able to do before:

• >Spelling suggestions if you right-click on a word. This will only work with Hunspell (as it requires real-time spell checking), but it was the number one requested feature by our users. 
• Enhanced predictive typing. In memoQ 6, capitalization, punctuation marks, etc. could prevent memoQ from showing some matches. This is a major improvement over that.
• Autopick. Just press Ctrl in a target segment and you will see the power of the new immersive editing experience. Autopick allows you to take over tags, term base entries, proper names, numbers, etc. from the source to the target without having to consult the translation results. I believe you will like it.
• Versioning improvements. We are rounding up memoQ's great version management which stores multiple source and target versions in the same document by allowing you to revert to any previous version or reject suggestions made by the proofreader.
• New quality assurance checks. First, there were some improvements to the check that compares the segment's translation with the best translation memory / LiveDocs match. It is now also possible to check the order of the tags which could have prevented successful export at times. When you get a terminology warning, memoQ now also suggests what's the right term, so it is easier to fix it on the Resolve errors and warnings pane. There are two improvements to the length check: you can now also check the length against a given amount of characters (i.e. all segments may not be longer than 50 characters), and you can also have double-byte characters calculated as two characters.
• 101% in LiveDocs. LiveDocs now offers you context matching, so some of you who wanted to completely replace TMs with LiveDocs can do so. This will not work with existing corpora, only with new corpora.
• Opening docs automatically after export. Optionally you can instruct Windows to automatically open the document or bilingual document that you exported, so you can immediately see if the export was correct, without having to find it and open it separately.
• Disable translation result types. If you don’t like certain match types in memoQ, you can now disable them. In memoQ 6 you were able to reorder them, but not disable them. Bliss for those who never wanted to see fragment assembly results.
• New filtering and sorting options. It is now possible to filter for X-translated segments, or filter for segments with tracked changes, filter for modifying users or segment modification time, and sort by segment status. Useful for the reviewer’s purposes.
• Multiple MT engines used at the same time. In older versions of memoQ you have to choose one single machine translation engine to be used during translation. With the new framework you can get matches from all of them at the same time, so if one is bad, you still can pick the good one.
• Improved X-translate. Ignored warnings and segment status makes it to the new version of the document. This is a big improvement that was requested for years, as this is the way to keep up automated QA meaningfully in a quickly changing source.
• Term prefix matching for Hebrew. memoQ's terminology recognition was optimized for languages that use suffixes - but some languages like Hebrew and Arabic, or to an extent also Scottish Gaelic, use prefixes rather. We managed to crack this for Hebrew, and Arabic is also coming soon. Well, not a lot of our users translate from Hebrew, but I think they will really appreciate this.

From a project manager's point of view, these are the big improvements:

• Document history in new workflows. FirstAccept, Groupsourcing, Subvendor Workflow and Slicing did not get a document history (Overview panel / History), a description and logging of all actions that happened in the previous version in memoQ 6. They get it now.
• Confidentiality mode in online projects. You can disable machine translation, external TM and term base engines, so the translator may not leak the document through cloud services.
• Better online project creation. We saved a few clicks here and there during online project creation, by adding Communication setup to the Publish wizard and by automatically opening the management mode after having created the project.
• Statistics and pre-translation for all languages at once. In the multilingual projects it wasn’t possible to run stats and pre-translation for all languages at once. Now it is, and this saves a lot of PM time.
• Delivering the statistics with the project. Especially with FirstAccept, the typical question before taking a document is to establish the word count. Project managers will be able to attach the statistics to the project’s notification message, so they do not need to be calculated separately, putting a burden on the server.