On Sat, Nov 3, 2012 at 1:09 PM, BIK Terminology— wrote:

> ** > Barbara Inge Karsch posted: “In the last few months, I have been > reading quite a bit about machine translation. And I also took the > opportunity at the recent LocWorld in Seattle and the ATA conference in San > Diego to attend sessions on MT. In Seattle, TAUS presented several > real-wor”

My suggestion would be that they really need to build in a way to hunt down and get rid of duplicates. Especially now that they have introduced a term extraction module, which I expect is going to create quite a few. I hope they are not just using this lack of functionality as a way of making us cough up the extra money for qTerm (whose price isn’t even listed).

As to the second problem (reimporting term bases), it wouldn’t exist if memoQ could clean duplicates. I think any decent tool ought to be able to handle its own data internally. This also applies to the TM editor in memoQ, which is basically … the ancient Olifant for many users.

In short, although I understand they are trying to target different types of users with their Pro and Server tools, data management really needs some work before they add any more new features. If you have access to a listening ear at Kilgray, this would basically be my number one feature request.

Best wishes,

Michael

Michael

Thanks for the note. You are addressing two problems: Duplicates in termbases and reimporting a termbase into memoQ. Neither one is a simple issue. But expectation would be that memoQ allow you to successfully export and reimport terminology. Of course, every human mistake in the export will be an issue upon the import. But I agree, it should be doable, if you do everything right.

As for duplicates in termbases, specifically in memoQ: Note that I haven’t looked at the most reason version of memoQ, but the interface of the termbase is not meant to support super-intensive terminology management. That was never Kilgray’s intent, if I understood them correctly. Less support by the tool does lead to a higher number of doublettes, for the simple reason that a lot less work goes into the individual entry, which means the translator doesn’t remember as much or have as much data to check on. I think it is a tradeoff that many translators are willing to go for: less time investment upfront, lower-quality data.
Is there a specific suggestion you have for the team?

Greetings from Antwerp. Barbara

I’m not sure how familiar you are with memoQ, but I was wondering if you had any tips on how to weed out duplicates in memoQ TBs? We have been asking Kilgray to fix this for a long time but no one seems to be listening. Several people have devised home-grown methods similar to what you mentioned – export to Excel, do the cleaning there, and then reimport – but they are never bullet-proof and my TBs never make it back in one piece.

Michael

I teach Terminology in Brazil. My students are translators to be and when I talk to them about job positions, such as this one you mentioned, they just laugh at me, not being able to imagine such a thing! I mean, a terminologist is a person they have never ever heard of. Now I can show them I real example.

Thank you!