Jun 14, 2014

Be Strong. Buy SDL Trados Studio today!

I've been testing the new memoQ 2014, thinking of all the great features I can and probably should describe, even promised to describe when Kilgray kindly gave me and other bloggers early access to a pre-release version. But, alas, I have a soft heart and cannot help but think of the despair SDL stockholders and employees must feel, the anguish of Studio users when the reality of their plight sinks in and they read the latest news about that apostate tool, memoQ, which just works most of the time instead of making you work for it.

The quote above from a long-suffering member of the SDL Trados beta test team is indicative of the emotions and experience of many veteran Trados users, and that colleague and so many others are fleeing to higher ground, hoping to find a place on Kilgray's software ark before the floods of Big, Dirty Data wash over the land and drown the #sdlinnovators as they desperately tease performance from their "vertical MT". And shocking revelations of translation practices in Maidenhead, UK, as reported by a neighbor and reformed SDL employee with a direct view of the SDL parking lot there, have led many to fear the Days of Revelation for memoQ 2014.

And I think of the SDL consultants and translation IT consultants in Germany who were only following orders when they helped their customers implement Across, and the despair they must feel at the thought of the many memoQ trials now being conducted in their country.

I think of all the things I could show and tell about the new project templates and automation in memoQ 2014, and all the hearts and minds that will break at the realization, the weeping and gnashing of teeth over wasted hours, years... and lives in the shadowed margins of struggling existence, gnawing on classic Wordfast crusts.

Workflow interoperability and general ease of use from Kilgray are threatening diversity in translation technology as the flocks of sheeple move to greener software pastures and eat their fill of easier language service provision and take a greater share of profits better devoted to those kinder, gentler providers of linguistic sausage.

So please, gentle people, do your part, show mercy and invest in endangered translation tools, which seek only to take us down that primrose path, paved with good intentions, to relieve the undue burdens of buyers who sacrifice far too much of their capital on the altar of survival for undeserving freelance translators. Support the Smartling crusade, offer your Maidenhead to SDL, keep your head in the XTM cloud as you practice your Fluency for languages, enjoy that nagging sense of Dejà Vu, source your memory and surf the storm-TAUS'd Big Wave and Google in awe at automatic translation on the active commodity market.

Friedrich Nietzsche wrote: "Was dich nicht umbringt macht dich nur stärker" ("what does not kill you only makes you stronger"). Be strong. Don't take the easy way out of Translation Tribulations with memoQ 2014. Get your SDL Trados Studio license here instead.


  1. Thanks Kevin! What great writing skills you have! I enjoyed this! Susie Z

    1. Thanks, Suzie. And I do hope that you are one of the few. The proud. (The SDL Trados Studio users.)

  2. At the moment I would not recommend the use of memoQ 2014 (I would recommend staying with memoQ 2013 instead).

    There is a really major bug that I (and other translators) have experienced:

    I create a project in memoQ 2014, using the same procedure I've followed previously with memoQ 2013 projects.
    After completing the procedure, I click on the project, and I don't see any files to open.

    If I then close memoQ 2014, switch back to memoQ 2013, and open the project, I can then see and work on the files.

    If i save those files after translating a few segments in memoQ 2013, then switch back to memoQ 2014, at this point I am able to open the project and see the files.

    Frankly, I don't understand how they could release the new version with such an enormous bug in it.

    1. Hi Riccardo,

      This issue only happens if you import the files from a shared folder/drive (\\file\\something.dox). It will be fixed with the release of 7.0.6 . In the meantime please use a local drive, and it should work perfectly.

      Gábor Nagy
      Support Engineer
      Kilgray Translation Technologies

    2. Hi Gabor,

      I imported from a local drive of my own computer (however a drive which is shared with other computers on my LAN). I'll be working in 2013 for the time being.



Notice to spammers: your locations are being traced and fed to the recreational target list for my new line of chemical weapon drones :-)