In the example above, for example, I am searching the 2 million translation unit EU DGT TM using text selected in a memoQ 6.2 project. Working this way offers me the following advantages:
- I can separate the concordances for my project from a big reference dataset I only need for certain lookups.
- A simple copy command (Ctrl+C) automatically looks up text in either language in the TM search tool.
- If I want to avoid any possibility of unintended "leakage" of data from certain TMs in the project, selecting them for use in the memoQ TM search tool ensures that their content will never be "accidentally" inserted as an ordinary TM match as I work.
I remember an argument with a translation agency owner about a year and half ago. The man told me quite insistently about his intent to force even translators with memoQ to use the web translation interface so that he could restrict them to the use of the client-specific TMs he maintained. With the use of the TM search tool, a reasonable compromise is achieved for TM data at least. (LiveDocs and termbase access remains a bit more cumbersome, however, though by setting up a dummy project with termbases, corpora and particular TMs attached, one could actually use three separate concordance sets. That could be interesting.)
In any case, the possibility of a separate concordance for handling large data volumes separately from one's main TMs and the possibility of doing this even while using older versions of memoQ may be a reason why those who do not yet want to do their routine work in the latest version or cannot do so can still benefit from upgrading now and installing the latest version alongside the old version(s).
Post a Comment
Notice to spammers: your locations are being traced and fed to the recreational target list for my new line of chemical weapon drones :-)