Discover memoQ 8.6
These are the most important new features of memoQ 8.6.
Until now, memoQ's CMS Connector only worked with WordPress's WPML XLIFF files. From version 8.6, it can handle any file format that memoQ server itself can. In the project templates used for CMS workflows, you can assign filters to different file types.
This enhancement opens up the possibility for wider integration: With some development effort, anyone can integrate their own CMS with memoQ server.
Also, memoQ server now backs up the CMS file system and configuration files.
Both memoQ and QTerm now have improved support for right-to-left languages such as Arabic, Hebrew or Urdu.
The popular PNG image format is now available in your term bases.
In the translation editor, a new right-click menu lets you copy term-level and entry-level metadata from the Translation results list to the clipboard, and paste them in other applications like Microsoft Word.
In the Term extraction editor, you can select text on the target side of the Occurrences pane, and add it directly to the current term candidate as Target term.
memoQ server's Web Services API now offers more terminology-related functions.
QA reports now also show the project's target languages, the number and names of checked documents, and the term bases used for QA. memoQ gives suggestions for issues related to auto-translation, both in the QA report and on the Resolve errors and warnings tab.
Our new filter can import different kinds of Visio files - both older formats and the ones from Visio 2013 and newer -, and export into the new formats. memoQ's composite filters now import Word documents and Excel sheets with embedded Visio drawings.
When importing a Transit TIPP package, memoQ now imports machine translation (MT) results into a separate TM.
In version 8.4, we introduced the Customer Insights Program, which, with your approval, collects anonymous data about how you use memoQ. From version 8.6, we extend data collection to memoQ server and the Deployment tool: we measure backup time and size, and the space taken up by different memoQ resources. This will help us reduce backup time and effort.