New feature for memoQ 4.2 or later: project archival. Backup and restore functionality for the project including TM and TB. Useful for moving projects to a new PC and keep two PCs in sync.
Speed degradation on network drives: it’s a problem created by the underlying input/output system.
More on archiving and paths. Suggestion to make relative path as the default. This suggestion is being considered.
In 4.2 a brand-new aligner is available. Interface has been reworked, improvements with multiple documents. Segments are editable.
Problems in handling Chinese/Japanese content:The focus from the input method editor shifts away from the main window. Developers are working to solve the problem. It appears to be a rather complex bug. There is also an alleged problem with fonts since version 4.0. If you copy Japanese text from the source to the target and the target uses a Latin-based font, you may get useless squares. However, most users translating from/to Japanese do not have a problem with this.
Dragon Naturally Speaking support: support in the 4.0 version has problems. These should be solved in version 4.2.
Feature request: hide the mouse pointer when the user starts typing. This is probably already supported by your mouse driver.
Plans to have a clone project feature for local projects.
Feature request: search for tags and/or filter for tags. It’s being considered.
Request: make the metadata from the term base visible in the translation environment. In all probability, qTerm will be addressing this issue.
Hunspell problem with the Rumanian dictionary. Perhaps the best solution is to replace the default dictionary with a new one.
Ctrl-shift-B – Ctrl-shift-N keyboard shortcut allows to move the selection to the left/right.
Request: if the source term is in small caps, insert it as small caps even if it’s capitalized in the target term base.
Fragment-assembling: often short segments from the TM take precedence over the same term from the term base. Sometimes the result is that a term is inserted with wrong capitalization. Perhaps this issue will be solved in qTerm. qTerm will also offer filtering capabilities.
Inverting the “direction” of translation memories. Version 4.5 will introduce features that will make this “problem” obsolete.
Inline tags: if you have translated a project containing bilingual files that use the “old” (inserted by F8) type of tags, and then receive a new version that use the “new” version tags (F9), your match rates will decrease because the tags are not substituted on-the-fly. This is something the developers are working on.
Request: LAN access to term bases and translation memories without using memoQ server: this is recognized as an important feature, but it’s not going to happen. Tiny translator groups still have to purchase the server version if they want to share resources.
Request: add a keyboard shortcut to add a term as untranslatable. This is being considered as an addition to future versions.