In yesterday's 298th Tool Box Journal from Jost, there were some more thoughts about new Cloud TB terminology and term matching with linguistic-based search.
The first column shows the word in the translatable file; the second the existing terms in the (then: MultiTerm) termbase that were present in the termbase but were erroneously not detected as matches; and in the third column you see terms that now were detected with the identical source text and an identical termbase, only this time in the Language Cloud and with morphology support. It was not perfect, but clearly a lot better than before. And not only better, but useful. You can also see that it not only supports morphological changes (gekauft -- kaufen, geladen -- laden) but also compound words, which -- believe me! -- is especially helpful in a language like German.
The same feature is also available for term verification (you know, the previously frustrating quality check that typically turned out way more false positives than real ones).
To discover the terms above, you'd need more than prefix matching and word stems. Any chances for the future?
Lässt sich denn hier: https://verben.woxikon.de/liste-deutsch und hier: http://www.canoo.net/services/Controller?input=beugen&MenuId=Search&service=canooNet&lang=de nix harvesten?
Ich antworte mal auf English.
There are several questions to pose:
>Isn t it better to have more, but then more precise terms (I assume this is our case)?
I do think so. Personally, I add alternative forms (plural, infinitive etc.) via macros. The 'new' feature that you can add multiple lines via the Add new term dialogue box, is very handy here.