Pages

Nov 23, 2010

memoQ brain surgery: getting rid of unwanted languages

This tip is by no means new. The discussion of this issue goes back at least to 2007, when Kilgray's head of development stated that it was planned to make this particular configuration a little user-friendlier but that it wasn't a high priority. He was certainly right about that given all the challenges the software has met in the meantime in its development. I think that memoQ is clearly the best value today for freelance translators and SMEs (LSPs or companies that require a lot of translation) on the market today. Costs are modest and the usability is usually much better than the competition. However, there are still a few geeky potholes left in the configuration where even a geek can step in and break his foot if he isn't careful.

This feature isn't as annoying as, say, any memoQ configuration involving regular expressions. If you want to learn some creative Western American English, come to Berlin, buy me five or six beers and say the words "regular expressions". Wear a flak jacket just in case.

Every time I set up a memoQ project I have to go through the project setup wizard. This is a routine that users of many similar tools must endure as well. Some of us try to get around this by creating pseudo-templates or "master projects", but for me these workarounds are simply annoying. I want real project templates I can invoke from a list.

In the project wizard, one of the chief annoyances for me is the list of languages from which I almost always choose the same settings: German and English (the generic variants for both). Rarely I'll go for the EN-US setting and once every three full moons maybe a bit of EN-GB if I've had too much cider. So when I see that long dropdown list with every sort of Chinese, Edo, French and a zillion other languages of no use to me, it's hard not to grumble. Even the shortcut of hitting the first letter doesn't help that much in German, because there are a good number of other languages that precede it under "G".

There are a number of possible solutions to this issue in software design. One fairly simple method used by a number of applications is to place the most frequently used languages at the top of the list. Microsoft Word seems to do this with its language settings, for example. Another approach I found interesting for a web interface is the one used by LSP.net for the Online Translation Manager, where the administrator can specify a list of languages that appear as shortcuts under the dropdown field:


The screenshot above is from an agency that works with quite a few languages; I think those are the nine most frequent ones. Oops. Make that ten. I have enough trouble keeping track of the two I work with.

If you want to cut down the list of languages in your memoQ installation, the procedure is "simple", but not really user-friendly and not without risk. You also have to remember to back up the altered configuration file, because it will be blasted into oblivion by the next update. (Not sure if this tip from Kilgray refers to major updates or the frequent little improvements that are released almost weekly.)

The procedure was described like this in an online wiki:

Hide target languages you don't need
  • Edit the LangInfo.xml file and comment out or delete the languages you don't need. You can use Notepad or an XML editor, your choice. Note: Be sure to save a copy of your edited file in a safe place, because a program update will overwrite it.
  • The file is found here:
    C:\Documents and Settings\All Users\Application Data\MemoQ\LangInfo.xml
Actually, this applies to source and target languages. And the path may vary depending on your version of memoQ and installation settings. I found the file on my new system here (after I changed the folder settings in the Windows to show hidden files):

With your handy MS Notepad or an XML editor, you're ready to perform brain surgery on the XML configuration file and comment out the languages you don't need using the HTML/XML comment markers to enclose them in the list:


Here I used the free application XML Marker for convenience. However, this can be done in any text editor. The result in the LangInfo.xml file looks like this:




And in the Project Wizard of memoQ, the streamlined menu looks like this:

Really, I could and should trim it further. In any case, this is a small time-saver, but little bits of time add up. Many people have wished for some sort of improvement to the process of selecting project languages (defaults, anyone?), and I hope that one of these days this can make it a little farther up the feature priority list in some form. Until then, Dear Reader, you know what to do. (And if you do it, don't forget to back up the file!)

5 comments:

  1. Thanks. The long list is very annoying, but not enough for me to do anything with it... yet. Now I'll now how to simplify the project setup process.

    ReplyDelete
  2. That's pretty much how it is with me too, Marek. I've changed LangInfo.xml several times, but then I forget to back the modified file up or put it on a new system. Thus the reminder (to myself as well) in green at the end.

    What worries me a little about telling people to chop down their language list this way is that those who do not understand tag mark-up run the risk of placing the comment markers in the wrong location so that the uncommented portions have an "unmatched" tag. I don't know how memoQ will react to this (nor have I felt like screwing up a file to test this).

    ReplyDelete
  3. Kevin, be careful with your wording. I am an eager learner, I love creative American English, and I might as well turn up in Berlin one day. I'll practice my pronunciation of "regular expressions" in the meantime.

    ReplyDelete
  4. unluckily, in memoQ 6.2 the LangInfo.xml disappeared ...
    so the translators ungrateful for the zillion-languages flood are punished
    GRRR

    ReplyDelete
  5. Perhaps you should look again, Claudio - it's still there.

    ReplyDelete

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