memoQ 5.0: Mr. Q Brings Change Management to the Localisation Continuum
Posted by Nick Peris on June 21, 2011
MemoQ 5.0 will be available as a public Release Candidate on June, 30 2011 and should reach Final Release within a few weeks of that.
The Release Candidate version can be installed side by side with memoQ 4.5 and various upgrade paths will be available to current memoQ users.
Following the strong focus on Project Management in memoQ 4, the philosophy behind memoQ 5.0 is Change Management. Changes in source files are better managed through X-translate, while segment changes are tracked through a sophisticated versioning system. Illustrated examples of this and other new features are detailed below.
memoQ 5.0 Version Tracking
The implementation of Major/Minor version control is powerful because of the simplicity with which it responds to a real need. A Translator is working on a file, receives an update to the source file, thanks to memoQ 5.0′s Major versioning feature, he or she can immediately generate an updated version of their bilingual file and continue translating.
There is no need to leverage, which would require a more labor intensive process of pre-translating again from Translation Memories. One can simply go straight from a partially translated copy of version 1.0 to a partically translated copy of version2.0.
The screencaps below show how to xTranslate a single file from the previous Major version of the file, then how the xTranslated segments are marked and finally how to save a snapshot of the resulting file.
It is also possible to export a 2-column file for comparison of 2 Major versions:
Change tracking enables segment level access to previous versions. The following images show how to enable custom track changes from the Translation menu, how the changes are highlighted in a document, and a further 2 options for translators and reviewers to see changes made to a file since they last edited it.
Terminology in memoQ 5.0
MemoQ 5.0 will allow a substantial amount of Terminology work without requiring the use of a dedicated application such as qTerm. Users will be able to extract candidate terms from a Project:
The use of Stop Words list will ensure easy noise reduction by preventing words such as “and”, “the”, or any other short listed by the user, from appearing as Candidate Terms:
Reviewing Candidate Terms
Candidate Terms can then be reviewed in context and possibly against an existing Termbase:
The Lexicon option will let you work with a Terms list without having to go through the full process of creating a Termbase. It is meant as an easy-to-use, immediately rewarding tool to manage Terminology within a Project. This should encourage Linguists to run quick Term extractions before starting a job, especially in cases where a Termbase is not available as part of the Handoff, in order to efficiently get a general overview of the Terms contained in a set of source files.
MemoQ 5.0′s Terminology feature does not support the TBX format, however Kilgray’s fully-fledged terminology tool qTerm, does.
memoQ 5.0 and nested file formats
Another very effective idea implemented in memoQ 5.0 is the support for file formats containing code belonging to other file formats. An obvious application is the case where the handoff is a spread sheet containing strings copied from an xml or a software file. But there are other common cases such as XML files containing HTML code.
The requirement here is to parse files twice so that all codes are recognised as such and so that the linguist can concentrate on translating with full confidence that all tagging is managed by the CAT tool. Here are 2 examples:
Source Content connectors
Finally, memoQ 5.0 will also in time be able to connect to repositories where content is dynamically added. It is designed with CMS integration in mind, however the CMS connectors will only be released later this summer, like the web-based editor webTranslate.