Heuristics for key term mismatch

General Discussion
1

Hi,

would that be possible to add some heuristics to key term mismatch check?

The way it works now makes it quite useless for e.g. Slavic languages:

Key Term Mismatch (iPod touch / iPod touch)
Learn what to do if your iPhone, iPad or iPod touch is lost or stolen
Dowiedz się, co zrobić w przypadku zgubienia lub kradzieży telefonu iPhone, iPada lub iPoda touch

Key Term Mismatch (Apple Support / Wsparcie Apple)
If you need additional help, contact Apple Support.
Jeśli nadal potrzebujesz pomocy, skontaktuj się ze Wsparciem Apple.

It should be self-explanatory where the problem lies…

1 Like
2

Two possible solutions:

  1. Use the key term glossary, but enter in it only the root part for the target language, so for example
    Support <tab> Wsparci
  2. Instead of using the key term glossary, add the terms to a personal or project checklist, where you can use regex to account for the different possible word endings, e.g.
    Apple Support Wsparci(e|em) Apple
    (This of course might need to be changed depending on how your language actually works… I often do this for Italian, for example so as to be able to use the same check for both singular and plural forms of a term, e.g.: “programm(a|i) di assistenza Apple”)
3

I am aware of these workarounds. They will not work at all in my workflows, in which I run Xbench over Studio projects with attached termbase. In such case, the keyterm file (from attached Multiterm) will be each time loaded from new file, which unables me to do any persisent changes in the keyterm file or to move these checks to the checklist.

Hence my heuristics request.

1 Like