Key terms, understanding MemoQ TB morphology


#1

Hi there,

any translator to Slavic languages can tell you how useless are typical terminological QAs with their lack of understanding for any morphology. As you may or may not know, Slavic languages have a strong tendency to modify base forms of a word in a myriad ways specific to a given context, sentence, etc. In Polish one noun can have at least 14 forms. This makes a typical strict terminological QA pretty useless, as the number of false positives is overwhelming.

However, MemoQ offers a nice solution to it — I can mark basic morphology in the TB. For example I can enter there:

car — samoch|ód
computer — komputer*

and let it be known, that only the root „samoch” should be considered for matching, as „ód” is only present in the nominative singular, and that „komputer” can be followed by some morphological suffixes. This will remove false positives from sentences like

I didn’t have either a car or a computer.
Nie miałem ani samochodu, ani komputera.

…which would be a case in a typical QA scenario.

And my big question is:

would it be possible for XBench to understand those two markings from MemoQ TBs and interpret them accordingly? This would be hugely beneficial mainly for Studio users, which doesn’t have any feature like this.

Best
Jarek

[can I consider this forum as a way to make „official” feature request? I want to make sure, as this is my first post here :slight_smile: ]


#2

Posting feature requests and suggestion here is perfectly fine because we monitor this forum. Bugs or urgent support requests are a bit less useful here because they often involve sending (sensitive) files, and also because our response time is usually faster in Support than it is here.

It seems a good idea that if a user spent time configuring custom glossary entries in memoQ, we try to leverage such investment for our Key Terms QA check if the glossary in question happens to be a memoQ termbase.

We will log a task in our DB to consider implementing support for memoQ Custom Matching pipe (|) and asterisk (*) characters if a memoQ TB is loaded as Key Terms.


#3

I support this request. The current Key Terms implementation gives a lot of false positives