In his presentation, Gábor did a good job of describing the benefits of the new features for the three major target groups: individual translators, language service providers (agencies) and enterprises. The major innovations in version 5.0 include:
- change tracking and versioning
- terminology extraction and a project lexicon
- an "on-the-fly" tagging feature (using regular expressions) for improved content filtering and protection
- cascading (sequential) filters for mixed context such as XML embedded in Excel files
- a source content connector interface for CMS integration, etc.
- initial analysis of project terminology with term extraction
- term precedence in fragment assembly with the project lexicon
- better handling of complex, mixed formats with the regex tagger and cascading filters
- selection of the termbase to which terms are added (supports better QA procedures)
- customized inclusion of tags in word and character counts to enable appropriate compensation for the extra effort involved in translating heavily tagged content
- viewing of corrections using the tracked changes features
- the new X-translate feature leverages previous work better and more accurately based on source documents, not TMs
- more accurate feedback with segment histories
- improved audit trail with reporting features
- automation via content connectors
- open interface for content management system (CMS) integration with memoQ
The regex tagger essentially enables custom tagging of any content, and the configurations can be saved and used sequentially with other filters. This would have been very useful in a number of projects I have done over the years, where HTML content was embedded in Excel or XML files and particular care was needed to avoid damaging the tags. I can also use this feature to protect placeholders in an ongoing localization project I do based on Java Properties files. Placeholders like [% COMPANY_NAME %] can be turned into tags and protected from damage. The tagger and the ability to chain file filters together are the features I find most personally interesting in the new version, though it is the terminology features I have wanted the most and for the longest time and shall benefit from in nearly every project. The combinations of sequential filters can also be saved for re-use.
The tracked changes feature and versioning will be extremely useful to those who have to deal with projects where new versions come fast and furious and it's easy to lose the overview. It also has a lot of potential to improve editing and review workflows. Changes can be displayed between any two document versions, and "snapshots" of work in progress can also be saved for purposes of work and comparison.
The new features I've described are by no means all of what we can expect in memoQ 5.0. Gabor mentioned a number of other things in passing, such as "watched folders", which I assume will enable some sort of file import automation in projects, but frankly there was so much to absorb, and I found myself dwelling on a number of personally exciting points, so that I missed other features which may also be of interest.
Version 5.0 will be published at the end of June as a release candidate (i.e. presumably table beta version), with the official release a few weeks later after the inevitable initial bugs are ironed out. During that transition period, a parallel installer will be available so that users can work safely with the current version 4.5 while still making the acquaintance of the new version.
Congratulations are due to the Kilgray team for the many important advances in the upcoming release. I also look forward to the effect this may have on the market: by setting the bar of innovation and usability higher than ever, Kilgray should further inspire its competitors to respond with interesting new features and variations on these new themes. And that will be good for all of us.
Nick Peris has another review of memoQ 5 based on the same presentation. It can be read on his blog here. The information on upgrade costs is not correct, I think. It's not a 20% discount but rather 20% of the base cost of a license in some cases (where it isn't free) - this is simply the usual Kilgray support fee policy.ReplyDelete
Error removed, thanks Kevin. Nick.ReplyDelete