Hacking Trados Freelance Languages

One of the great nuisances for me in working with Trados is the limitation of the freelance version with respect to the languages that can be set. Only five are permitted at a time. If for some reason you need to make changes, the standard advice is to uninstall the application, clean the registry and re-install. All in all a fairly time-consuming process if you are used to more streamlined CAT tools that install in 5 minutes or less. And work afterward. Also, when I install SDL Trados Anything on my Windows 7 system with all the latest schnick-schnack and see Win XP components and runtime engines with dates like 2005 being hammered onto my system, I am... well... just a little concerned. One of these days I expect SDL will refactor its software to make it more scalable and able to match the performance of other leading applications. Until then I will tread carefully with anything involving installation.

All in all, registry hacking, though generally spoken of in fearful terms, is probably the safer, gentler alternative for adjusting the five languages set for Trados. Why would I want to do that, you ask? Although I actually only work with two languages and amuse myself with another two, I get sample files in various combinations I would never dream of handling with requests to look briefly at some technical issue. This week it involves Polish. Up to now my main concern with the Polish language has been to discipline myself not to mistake it for Russian when I've passed 20 shots sampling the variety of vodkas in polite company in that fine country. But today I had to open a TWB TM with English and Polish, and my friend the Flagman said it was verboten.

Fortunately, others have gone before, deciding it's bullshit to waste time re-installing the software for such a little thing, and after a bit of Google Searching I found that the necessary key to hack is the value at HKEY_LOCAL_MACHINE > SOFTWARE > TRADOS > Shared > IDNG:

Alles klar? Various users then revealed the Masonic secret of the key: the last ten digits are five groups of two digits each, with each two digit group being a hex code for a given language. Crikey. I take it all back about memoQ regex being obscure. The last part of my key was originally set to

-005D534D5847

with the last ten digits resolving to

5D - English
53 - German
4D - Russian
58 - French
47 - Dutch

In the screenshot above I've already changed French to Polish (41). After rebooting the computer, everything worked fine and I could have a quick look at the files.

A short list of codes that was shared in the discussion thread had a few errors, which were corrected by other contributors. I'm sure that a bit of research will turn up any other codes needed.

No language set = 84

Afrikaans 67
Azeri 78
Basque 79
Belarusian 77
Bulgarian 56
Catalan 57
Croatian 4E
Czech 51
Danish 52
Dutch 47
English 5D
Estonian 71
Faeroese 60
Finish 5F
French 58
Gaelic 62
German 53
Greek 5C
Hungarian 5A
Icelandic 5B
Indonesian 75
Italian 44
Latvian 72
Lithuanian 73
Macedonian 7B
Malay 63
Maltese 61
Norwegian 40
Polish 41
Portuguese 42
Romanian 4C

For further details, have a look at http://tech.dir.groups.yahoo.com/group/TW_users/message/56130.

memoQfest 2012: another great year and great things ahead

Some say translation technology has gone to the dogs, and

this was certainly the case in Budapest this year as Ajax

and Benny noted to their satisfaction.

Although I was first asked to consider memoQ by a client of mine in 2007 and actually began to look it a year later, I was very skeptical about the software when István Lengyel convinced me to take a break for the first memoQfest at the Benzcur Hotel in Budapest in 2009. I had seen interesting progress in the year I had tested the software, but it was simply too immature for my needs and lacked nearly all the features which were most important to me. About a week before the conference, Kilgray released a version that barely met my minimum requirements for a small portion of my clients. I was impressed and actually did my first bit of commercial work with memoQ - a press release - the night before the conference began. The event itself was a blast, and I was convinced that this team had the right stuff or at least the potential to make it.

The next two years confirmed the wisdom of this leap of faith as the company raced from strength to strength despite a few stubbed toes; the advance of memoQ clearly played a role in improving other leading tools like DVX and SDL Trados, the latter borrowing generously from Hungarian innovation or using it and the unmatched service ethos on the Danube as an inspiration to overhaul the catastrophic mess of legacy Trados and enter the modern age of CAT tools, even surpassing memoQ in a few points, though with the current Renaissance of creative development in what appeared just a few years ago to be a dead-end IT ghetto, it's not an easy guess as to who will stay ahead anywhere for long. These are indeed good times for users despite the renewed threats of lock-in posed by the current misguided server politics of most providers.

Nonetheless, Kilgray's rapid growth has not been without difficulties, and despite anticipating most of the challenges long before they arose, the team doesn't always put in the performance its demanding fans expect. This is often to be expected when a company experiences the exponental growth which can obscure long-turm interests in the confusing melee of daily business. And the product which seemed so fresh and clean just a few years ago is beginning to look like a car that has been taken on too many roatrips without a good cleaning, has hauled too many dogs and needs new tires. But last week I saw clear signs that there may be a new Maserati getting a tune-up in the development garage. The hints regarding memoQ 6 and the company's further roadmap led me to scratch of most of the items on my technical gripe list. The organizational wishlist has gotten longer, but it's clear that the "refactoring" process at Kilgray is not limited to the software, so I think I can trust them as I did four years ago when few could have anticipated the company's impressive track record.

I almost did not go to Budapest this year. When I read the published schedule, it sounded far too skewed toward corporate interests, a bit like a sell-out now that server sales revenue has far surpassed that from Translator Pro licenses. And bad calls like the confused differences in implementation of versioning features in memoQ 5, weariness from providing support for issues arising from a lack of professional service consulting in the sales process with some of my agency clients and my own stupidity of forgetting to vaccinate my puppy against rabies before the trip (which required me to leave him with someone else for the first time) had me considering a week of vacation at home.

That would have been a mistake. I only expected to draw value from one presentation - regular expressions by Polish guru Marek Pawelec - and even there I didn't expect to understand very much. Instead, every one of the rather random sessions I attended had a lot to offer, even for a freelancer. The agency presenters who talked about their approaches to challenges in complex translation projects shared a great deal of information that is directly relevant to my agency and direct client business and can help make it better. And the general talk on refactoring your business through innovation by Richard Brooks, which I expected to be the biggest hot air balloon of the week, was the absolute highlight for me. I might even have gotten something out of the Asia Online keynote on machine translation, though an idiotic quote I read from the speaker about how we need to get on the MT boat or drown suggests perhaps not. I do hold out some hope he might have been misquoted or taken out of context, however. It's the least I can do in a world where people still believe in the Tooth Fairy and US Republican politics.

When Kilgray releases the videos of the talks, do watch them. I do hope the sound and picture quality will be good, because too often I really did wish I could have been in two rooms at once.

The Twitstream shared a lot of the gritty details of the presentations; the hashtag #memoQfest or an archive established by a Ukrainian user will show these for a while at least. And I'll be drawing on the tweets, my other notes and the memories of conversations in the breaks to share insights, many quite trivial, all of which confirm that memoQ is the right choice for most of my translation IT needs. The only thing I'll say now is that in memoQ 6 the versioning features will be the same in all editions of memoQ. Big deal. For some of us.

Oh yes, and next year's memoQ fest might not be in Budapest. If I weren't visiting that city with some frequency now for dogs, I might be disappointed, because I love it and the rest of the country I have seen, but the change is unlikely to be a problem, because what makes Kilgray's memoQ truly great is not the venue and not the rather good technology, but the people: the ones who make it and the ones who use it.