Can't find plural for QA check

Technical Support
1

We expect turning off this option could avoid “Match Whole Words”

20220227231843
20220227231843904×370 16.1 KB

However, when we made the following keyterm list, we couldn’t check plural form.

Keyterm list:
English: risen god
French: dieu ressuscité

We’d like to detect this sentence:
Source:For the risen gods!
Translation: Pour le dieu déterré!

Ideally, we should find the translation didn’t follow the keyterm.
But, we couldn’t use “risen god” to find “risen gods” due to the plural form.

Does anyone know any solution to the issue except using regex?

2

Hi! I create check lists with terminology rather then using the key term check. But you have to use RegEx search then.

Source: risen god
Target: -“dieu ressuscité”
then CTRL+P = PowerSearch (not directly the search button)

Best regards
Burim

3

If the Match Whole Words in QA Check for Key Terms checkbox is disabled, the Key Terms Mismatch feature only affects the target term. That means that the source key term is considered Match Whole Word by default.

As @Burim states, the best approach would be to use checklists.

The following post may interest you.

4

Hello, I’ve been using Xbench for over 10 years and bumped into the same problem.
I have a habit of keeping a “key term” list of basic words such as “data” and “model” to avoid obvious omissions.
Today I found that a key term list for “input” does not apply to “inputs”. I think it was not this way in 2.9 and earlier versions of 3.0…(I remember word stems worked in older days.)
I tried the “key term list to checklist” exe on Github explained above, but it produced errors for a Japanese UTF-16 file.
I understand the current workaround is either to compile a checklist or include every form of nouns and verbs (plurals, past, past perfect, etc.) but I appreciate it if word stems can be used as a key term in the future. Thank you for your consideration!

1 Like